8000 [JENKINS-33623] Proxy configured in a wrong way by recena · Pull Request #58 · jenkinsci/github-branch-source-plugin · GitHub
[go: up one dir, main page]

Skip to content

[JENKINS-33623] Proxy configured in a wrong way #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 6, 2016

Conversation

recena
Copy link
Contributor
@recena recena commented May 24, 2016

JENKINS-33623

@reviewbybees

Thank @schulzh for reporting the issue.

@recena
Copy link
Contributor Author
recena commented May 24, 2016

@schulzh What do you think as alternative to #48?

@schulzh
Copy link
schulzh commented May 25, 2016

@recena It looks like a good solution

@recena
Copy link
Contributor Author
recena commented May 25, 2016

@schulzh My first option was to use your PR but I wanted to clean up some details. At any rate, thank you so much for your work.

@amuniz
Copy link
Member
amuniz commented May 25, 2016

🐝

@recena recena merged commit b20d0ca into jenkinsci:master Jun 6, 2016
@recena recena deleted the JENKINS-33623 branch June 6, 2016 20:35
@freeman
Copy link
freeman commented Jun 21, 2016

Hi,

I really want to use this plugin but this fix is blocking me at the moment. Any ETA on its release ?

Thanks for the great work on the github integration story in Jenkins !

@freeman
Copy link
freeman commented Jul 1, 2016

By the way I tested it by compiling the master branch and deploying it and it works beautifully.

dubrsl pushed a commit to dubrsl/github-branch-source-plugin that referenced this pull request Oct 17, 2020
Remove 'console' from build url in gitlab comment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0