[JIRA] (JENKINS-36119) GhprbBuilds creates wrong GhprbCause: merged vs. mergeable
Title: Message Title Jens Elkner created an issue Jenkins / JENKINS-36119 GhprbBuilds creates wrong GhprbCause: merged vs. mergeable Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 2016/Jun/21 7:56 PM Environment: jenkins 2.9, ghprb plugin 1.32.5 Priority: Blocker Reporter: Jens Elkner org.jenkinsci.plugins.ghprb.GhprbBuilds creates a GhprbCause, but unfortunately assigns the PR.isMergeable property to GhprbCause.merged (see line 58), which in turn causes other "wrong decisions" later (e.g. wrong sha1 env variable - see GhprbTrigger.java line 359). Add Comment
[JIRA] [ghprb-plugin] (JENKINS-35658) Re-built plugin does not work: webhook - No valid crumb
Title: Message Title Jens Elkner closed an issue as Fixed JDK related Jenkins / JENKINS-35658 Re-built plugin does not work: webhook - No valid crumb Change By: Jens Elkner Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-35658) Re-built plugin does not work: webhook - No valid crumb
Title: Message Title Jens Elkner commented on JENKINS-35658 Re: Re-built plugin does not work: webhook - No valid crumb Hmmm, switching from JDK 1.8.0_77-b03 to 1.8.0_92-b14 seems to solve the problem - really strange. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-35658) Re-built plugin does not work: webhook - No valid crumb
Title: Message Title
Jens Elkner created an issue
Jenkins / JENKINS-35658
Re-built plugin does not work: webhook - No valid crumb
Issue Type:
Bug
Assignee:
Honza Brázdil
Components:
ghprb-plugin
Created:
2016/Jun/13 6:32 AM
Environment:
Jenkins 2.8, ghprb 1.32.4, JDK 1.8
Priority:
Blocker
Reporter:
Jens Elkner
To be able to do some research on ghprb, I've cloned https://github.com/jenkinsci/ghprb-plugin.git, checked out ghprb-1.32.4, and built it with mvn clean package. Tests go through w/o any problem (Tests run: 53, Failures: 0, Errors: 0, Skipped: 0).
Now the odd thing: With the original version installed via jenkins update center (which is 1.32.4 as well), webhook delivery via GitHub work. But as soon as I "scp $ {BUILD_DIR}
/target/ghprb.jar $ {JENKINS_HOST}
:$ {JENKINS_HOME}
/plugins/ghprb/WEB-INF/lib/ghprb.jar" and restart jenkins on this host, webhook delivery fails with
Jun 13, 2016 8:10:55 AM hudson.security.csrf.CrumbFilter doFilter WARNING: No valid crumb was included in request for /ghprbhook/. Returning 403.
[JIRA] [credentials-binding-plugin] (JENKINS-26844) Job fails if 'Use secret text(s) or file(s)' is selected but none are configured
Title: Message Title
Jens Elkner commented on JENKINS-26844
Re: Job fails if 'Use secret text(s) or file(s)' is selected but none are configured
With Jenkins 2.8 and GitHub Pull Request Builder (ghprb) 1.32.4 the whole env variable settings get screwed up, when 'Use secret text(s) or file(s)' gets enabled. I.e. the Environment Variables section in build reports disappears completely, or if on uses the build-name-setter (1.6.5) e.g. with "#$ {BUILD_NUMBER} ${GIT_BRANCH}@${ghprbTargetBranch} ${ghprbGhRepository}/pull/${ghprbPullId} (${ghprbActualCommitAuthor})" everything except the "#${BUILD_NUMBER}
" disappears as well (and my guts say, what we see is just a fallback alias default value).
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-35224) apt-get upgrade jenkins fails (not POSIXLY_CORRECT)
Title: Message Title Jens Elkner commented on JENKINS-35224 Re: apt-get upgrade jenkins fails (not POSIXLY_CORRECT) Why not use service like this: --- /tmp/jenkins.postinst.orig 2016-06-06 06:03:10.0 +0200 +++ /tmp/jenkins.postinst 2016-06-10 15:33:14.215074484 +0200 @@ -85,7 +85,7 @@ if [ ! -e "/etc/init/jenkins.conf" ]; then update-rc.d jenkins defaults >/dev/null fi - invoke-rc.d jenkins start || exit $? + service jenkins start || exit $? fi # End automatically added section Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-30327) Failed to scout MultiJobBuildSelector - ClassNotFoundException: hudson.plugins.copyartifact.BuildSelector
Title: Message Title Jens Elkner commented on JENKINS-30327 Re: Failed to scout MultiJobBuildSelector - ClassNotFoundException: hudson.plugins.copyartifact.BuildSelector Same for jenkins 2.7 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-27045) Cannot use jenkins-cli with github oauth plugin
Title: Message Title Jens Elkner commented on JENKINS-27045 Re: Cannot use jenkins-cli with github oauth plugin Result Jenkins 2.7 Plugins: cloudbees-folder/5.11 junit/1.13 script-security/1.19 matrix-project/1.7 antisamy-markup-formatter/1.3 pam-auth/1.2 windows-slaves/1.1 mailer/1.17 ldap/1.12 token-macro/1.12.1 icon-shim/2.0.3 matrix-auth/1.4 external-monitor-job/1.4 build-timeout/1.16 credentials/2.0.7 structs/1.1 workflow-step-api/2.1 plain-credentials/1.2 credentials-binding/1.7 timestamper/1.8.2 ws-cleanup/0.29 ant/1.3 gradle/1.24 jquery-detached/1.2.1 durable-task/1.10 workflow-api/2.0 workflow-support/2.0 workflow-job/2.2 pipeline-rest-api/1.4 handlebars/1.1.1 momentjs/1.1.1 pipeline-stage-view/1.4 pipeline-build-step/2.1 ace-editor/1.1 workflow-scm-step/2.0 scm-api/1.2 workflow-cps/2.4 ssh-credentials/1.12 git-client/1.19.6 git-server/1.6 workflow-cps-global-lib/2.0 branch-api/1.9 workflow-multibranch/2.5 workflow-durable-task-step/2.0 pipeline-input-step/2.0 pipeline-stage-step/2.1 workflow-basic-steps/2.0 workflow-aggregator/2.1 javadoc/1.3 github-api/1.75 git/2.4.4 github/1.19.1 github-branch-source/1.7 github-organization-folder/1.3 email-ext/2.42 maven-plugin/2.13 dashboard-view/2.9.9 build-name-setter/1.6.5 embeddable-build-status/1.9 rebuild/1.25 throttle-concurrents/1.9.0 analysis-core/1.77 checkstyle/3.46 htmlpublisher/1.11 parameterized-trigger/2.30 jquery/1.11.2-0 build-pipeline-plugin/1.5.3.1 run-condition/1.0 conditional-buildstep/1.3.3 envinject/1.92.1 jenkins-multijob-plugin/1.21 git-parameter/0.5.1 role-strategy/2.2.0 emailext-template/0.4 publish-over-ssh/1.14 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and
[JIRA] [github-oauth-plugin] (JENKINS-27045) Cannot use jenkins-cli with github oauth plugin
Title: Message Title Jens Elkner commented on JENKINS-27045 Re: Cannot use jenkins-cli with github oauth plugin Ehmmm, nope. Per default it works w/o any problems: # java -jar ~/tmp/jenkins-cli.jar -noKeyAuth login --username root Password: # java -jar ~/tmp/jenkins-cli.jar -noKeyAuth help logout java -jar jenkins-cli.jar logout Deletes the credential stored with the login command. # java -jar ~/tmp/jenkins-cli.jar -noKeyAuth logout # java -jar ~/tmp/jenkins-cli.jar -noKeyAuth help logout ERROR: You must authenticate to access this Jenkins. Use --username/--password/--password-file parameters or login command. Just to make sure, here the complete list of installed plugins: ls -1 plugins/*.jpi plugins/ace-editor.jpi plugins/analysis-core.jpi plugins/ant.jpi plugins/antisamy-markup-formatter.jpi plugins/branch-api.jpi plugins/build-name-setter.jpi plugins/build-pipeline-plugin.jpi plugins/build-timeout.jpi plugins/checkstyle.jpi plugins/cloudbees-folder.jpi plugins/conditional-buildstep.jpi plugins/credentials-binding.jpi plugins/credentials.jpi plugins/dashboard-view.jpi plugins/durable-task.jpi plugins/email-ext.jpi plugins/emailext-template.jpi plugins/embeddable-build-status.jpi plugins/envinject.jpi plugins/external-monitor-job.jpi plugins/git-client.jpi plugins/git-parameter.jpi plugins/git-server.jpi plugins/git.jpi plugins/github-api.jpi plugins/github-branch-source.jpi plugins/github-organization-folder.jpi plugins/github.jpi plugins/gradle.jpi plugins/handlebars.jpi plugins/htmlpublisher.jpi plugins/icon-shim.jpi plugins/javadoc.jpi plugins/jenkins-multijob-plugin.jpi plugins/jquery-detached.jpi plugins/jquery.jpi plugins/junit.jpi plugins/ldap.jpi plugins/mailer.jpi plugins/matrix-auth.jpi plugins/matrix-project.jpi plugins/maven-plugin.jpi plugins/momentjs.jpi plugins/pam-auth.jpi plugins/parameterized-trigger.jpi plugins/pipeline-build-step.jpi plugins/pipeline-input-step.jpi plugins/pipeline-rest-api.jpi plugins/pipeline-stage-step.jpi plugins/pipeline-stage-view.jpi plugins/plain-credentials.jpi plugins/publish-over-ssh.jpi plugins/rebuild.jpi plugins/role-strategy.jpi plugins/run-condition.jpi plugins/scm-api.jpi plugins/script-security.jpi plugins/ssh-credentials.jpi plugins/structs.jpi plugins/throttle-concurrents.jpi plugins/timestamper.jpi plugins/token-macro.jpi plugins/windows-slaves.jpi plugins/workflow-aggregator.jpi plugins/workflow-api.jpi plugins/workflow-basic-steps.jpi plugins/workflow-cps-global-lib.jpi plugins/workflow-cps.jpi plugins/workflow-durable-task-step.jpi plugins/workflow-job.jpi plugins/workflow-multibranch.jpi plugins/workflow-scm-step.jpi plugins/workflow-step-api.jpi plugins/workflow-support.jpi plugins/ws-cleanup.jpi If you need more information/configuration, please let me know.
[JIRA] [github-oauth-plugin] (JENKINS-27045) Cannot use jenkins-cli with github oauth plugin
Title: Message Title
Jens Elkner commented on JENKINS-27045
Re: Cannot use jenkins-cli with github oauth plugin
BTW: Not sure what 'Jenkins CLI no longer uses --username and --password options' means in this context. At least 2.7 incl. cli works as expected, when oauth gets {not|un}
installed.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-27045) Cannot use jenkins-cli with github oauth plugin
Title: Message Title Jens Elkner reopened an issue Unfortunately this droves me crazy: java -jar ~/tmp/jenkins-cli.jar -noKeyAuth help login ERROR: You must authenticate to access this Jenkins. Use --username/--password/--password-file parameters or login command. And than java -jar ~/tmp/jenkins-cli.jar -noKeyAuth login --username foobar ERROR: "--username" is not a valid option java -jar jenkins-cli.jar login Saves the current credential to allow future commands to run without explicit credential information. java -jar ~/tmp/jenkins-cli.jar -noKeyAuth login foobar ERROR: No argument is allowed: foobar java -jar jenkins-cli.jar login Saves the current credential to allow future commands to run without explicit credential information. So it is awefully misleading and one gets stuck because there is no way to find out, how to get it work. Jenkins / JENKINS-27045 Cannot use jenkins-cli with github oauth plugin Change By: Jens Elkner Resolution: Cannot Reproduce Status: Closed Reopened Add Comment
[JIRA] [packaging] (JENKINS-35224) apt-get upgrade jenkins fails (not POSIXLY_CORRECT)
Title: Message Title Jens Elkner created an issue Jenkins / JENKINS-35224 apt-get upgrade jenkins fails (not POSIXLY_CORRECT) Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: packaging Created: 2016/May/31 4:05 AM Environment: Ubuntu 15.04, jenkins 2.6 installed Labels: jenkins Priority: Minor Reporter: Jens Elkner Upgrade from jenkins 2.6 to 2.7 fails if the environment variable POSIXLY_CORRECT is set (which is the default on all of our servers): > + apt-get upgrade jenkins Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... jenkins is already the newest version. Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up jenkins (2.7) ... * Starting Jenkins Continuous Integration Server
