[JIRA] (JENKINS-60426) All stages show up as UNSTABLE when one stage is unstable
Title: Message Title Nicholas Brown edited a comment on JENKINS-60426 Re: All stages show up as UNSTABLE when one stage is unstable Dupe of JenkinsJENKINS JENKINS -58783 ?Which was created as a result of: https://issues.jenkins-ci.org/browse/JENKINS-39203?focusedCommentId=372584#comment-372584 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203498.157599677.4003.1578409800511%40Atlassian.JIRA.
[JIRA] (JENKINS-60426) All stages show up as UNSTABLE when one stage is unstable
Title: Message Title Nicholas Brown commented on JENKINS-60426 Re: All stages show up as UNSTABLE when one stage is unstable Dupe of JenkinsJENKINS-58783 ? Which was created as a result of: https://issues.jenkins-ci.org/browse/JENKINS-39203?focusedCommentId=372584#comment-372584 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203498.157599677.4000.1578409800447%40Atlassian.JIRA.
[JIRA] (JENKINS-59804) Support Multibranch Pipelines
Title: Message Title Nicholas Brown commented on JENKINS-59804 Re: Support Multibranch Pipelines For what it's worth the https://plugins.jenkins.io/cloudbees-bitbucket-branch-source plugin works very well for using Bitbucket Server with multi-branch pipelines. It uses the Bitbucket Server native webhooks support. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202534.1571228736000.9775.1576590060329%40Atlassian.JIRA.
[JIRA] (JENKINS-46722) alwaysLinkToLastBuild not linking to last job result
Title: Message Title
Nicholas Brown commented on JENKINS-46722
Re: alwaysLinkToLastBuild not linking to last job result
I'm seeing this issue. The workaround to access the report suggested by Martin Røssland does not work for me. In the build log I see:
[Pipeline] publishHTML
[htmlpublisher] Archiving HTML reports...
[htmlpublisher] Archiving at PROJECT level /var/lib/jenkins/workspace/project_code_master/clangScanBuildReports to /var/lib/jenkins/jobs/project/jobs/code/branches/master/htmlreports/clang_20scan-build_20Static_20Analysis_20Report
and as mentioned in the this Jira ticket there is no link in the sidebar of the build. Trying to directly access the report results in:
HTTP ERROR 404
Problem accessing /jobs/project/jobs/code/branches/master/htmlreports/clang_20scan-build_20Static_20Analysis_20Report/index.html. Reason:
Not Found
The publishHTML step is being used in a post failure section of stage in a pipeline:
post {
failure {
publishHTML target: [
allowMissing: false,
alwaysLinkToLastBuild: false,
keepAll: false,
reportDir: 'clangScanBuildReports',
reportFiles: 'index.html',
reportTitles: 'clang scan-build Static Analysis',
reportName: 'clang scan-build Static Analysis Report'
]
}
Add Comment
[JIRA] (JENKINS-46722) alwaysLinkToLastBuild not linking to last job result
Title: Message Title Nicholas Brown updated an issue Jenkins / JENKINS-46722 alwaysLinkToLastBuild not linking to last job result Change By: Nicholas Brown Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185068.1504796587000.2150.1568300406082%40Atlassian.JIRA.
[JIRA] (JENKINS-57942) Found multiple extensions which provide method originPullRequestDiscoveryTrait
Title: Message Title Nicholas Brown commented on JENKINS-57942 Re: Found multiple extensions which provide method originPullRequestDiscoveryTrait Is this a duplicate of JENKINS-45504 ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199918.1560187438000.1778.1564147920287%40Atlassian.JIRA.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Nicholas Brown commented on JENKINS-53767 Re: Offer plugin management tooling This might help address the following ansible jenkin plugin management problem: https://github.com/ansible/ansible/issues/24864 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194275.1537882941000.1674.1562231341321%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47503) Abort ongoing builds of PR if new change to the same PR was submitted
Title: Message Title Nicholas Brown commented on JENKINS-47503 Re: Abort ongoing builds of PR if new change to the same PR was submitted Liam Newman just porting assumes the code that implements the behavior is the same for each plugin. They may work in different ways. Beyond that, I'm also not familiar with the code or implementation design/behaviors of either plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185960.1508335272000.16139.1559166060233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57746) provide issue IDs associated with a Pull Request
Title: Message Title
Nicholas Brown updated an issue
Jenkins / JENKINS-57746
provide issue IDs associated with a Pull Request
Change By:
Nicholas Brown
Currently the bitbucket branch source plugin provides the following environment variables:"BRANCH_NAME""CHANGE_ID""CHANGE_TARGET""CHANGE_BRANCH""CHANGE_FORK""CHANGE_URL""CHANGE_TITLE""CHANGE_AUTHOR""CHANGE_AUTHOR_DISPLAY_NAME""CHANGE_AUTHOR_EMAIL""TAG_NAME""TAG_TIMESTAMP""TAG_UNIXTIME""TAG_DATE"It would be very useful if this was extended to provide any issue IDs associated with a Pull Request ("CHANGE" in the above semantics).BitBucket Server provides a REST API to get issue IDs associated with a PR:{ { noformat} /rest/jira/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId}/issues {noformat } } https://docs.atlassian.com/bitbucket-server/rest/5.3.0/bitbucket-jira-rest.htmlPerhaps this could be exposed by the plugins EnvironmentContributor extension as something like "CHANGE_ISSUES" ?This would allow for use of the various Jira plugin steps to do things like update Jira tickets with information from a pipeline build of a pull request.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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
[JIRA] (JENKINS-57746) provide issue IDs associated with a Pull Request
Title: Message Title
Nicholas Brown updated an issue
Jenkins / JENKINS-57746
provide issue IDs associated with a Pull Request
Change By:
Nicholas Brown
Currently the bitbucket branch source plugin provides the following environment variables:"BRANCH_NAME""CHANGE_ID""CHANGE_TARGET""CHANGE_BRANCH""CHANGE_FORK""CHANGE_URL""CHANGE_TITLE""CHANGE_AUTHOR""CHANGE_AUTHOR_DISPLAY_NAME""CHANGE_AUTHOR_EMAIL""TAG_NAME""TAG_TIMESTAMP""TAG_UNIXTIME""TAG_DATE"It would be very useful if this was extended to provide any issue IDs associated with a Pull Request (" CHANGE CHANGE_ " in the above semantics).BitBucket Server provides a REST API to get issue IDs associated with a PR:{noformat}/rest/jira/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId}/issues{noformat}https://docs.atlassian.com/bitbucket-server/rest/5.3.0/bitbucket-jira-rest.htmlPerhaps this could be exposed by the plugins EnvironmentContributor extension as something like "CHANGE_ISSUES" ?This would allow for use of the various Jira plugin steps to do things like update Jira tickets with information from a pipeline build of a pull request.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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
[JIRA] (JENKINS-57746) provide issue IDs associated with a Pull Request
Title: Message Title
Nicholas Brown updated an issue
Jenkins / JENKINS-57746
provide issue IDs associated with a Pull Request
Change By:
Nicholas Brown
Currently the bitbucket branch source plugin provides the following environment variables:"BRANCH_NAME""CHANGE_ID""CHANGE_TARGET""CHANGE_BRANCH""CHANGE_FORK""CHANGE_URL""CHANGE_TITLE""CHANGE_AUTHOR""CHANGE_AUTHOR_DISPLAY_NAME""CHANGE_AUTHOR_EMAIL""TAG_NAME""TAG_TIMESTAMP""TAG_UNIXTIME""TAG_DATE"It would be very useful if this was extended to provide any issue IDs associated with a Pull Request ("CHANGE" in the above semantics).BitBucket Server provides a REST API to get issue IDs associated with a PR: {{ /rest/jira/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId}/issues }} https://docs.atlassian.com/bitbucket-server/rest/5.3.0/bitbucket-jira-rest.htmlPerhaps this could be exposed by the plugins EnvironmentContributor extension as something like "CHANGE_ISSUES" ?This would allow for use of the various Jira plugin steps to do things like update Jira tickets with information from a pipeline build of a pull request.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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
[JIRA] (JENKINS-57746) provide issue IDs associated with a Pull Request
Title: Message Title
Nicholas Brown created an issue
Jenkins / JENKINS-57746
provide issue IDs associated with a Pull Request
Issue Type:
Improvement
Assignee:
Unassigned
Components:
bitbucket-branch-source-plugin
Created:
2019-05-29 15:45
Priority:
Minor
Reporter:
Nicholas Brown
Currently the bitbucket branch source plugin provides the following environment variables: "BRANCH_NAME" "CHANGE_ID" "CHANGE_TARGET" "CHANGE_BRANCH" "CHANGE_FORK" "CHANGE_URL" "CHANGE_TITLE" "CHANGE_AUTHOR" "CHANGE_AUTHOR_DISPLAY_NAME" "CHANGE_AUTHOR_EMAIL" "TAG_NAME" "TAG_TIMESTAMP" "TAG_UNIXTIME" "TAG_DATE" It would be very useful if this was extended to provide any issue IDs associated with a Pull Request ("CHANGE" in the above semantics). BitBucket Server provides a REST API to get issue IDs associated with a PR: /rest/jira/1.0/projects/ {projectKey} /repos/ {repositorySlug} /pull-requests/ {pullRequestId} /issues https://docs.atlassian.com/bitbucket-server/rest/5.3.0/bitbucket-jira-rest.html Perhaps this could be exposed by the plugins EnvironmentContributor extension as something like "CHANGE_ISSUES" ? This would allow for use of the various Jira plugin steps to do things like update Jira tickets with information from a pipeline build of a pull request.
[JIRA] (JENKINS-56802) support credentials for authenticationToken
Title: Message Title
Nicholas Brown created an issue
Jenkins / JENKINS-56802
support credentials for authenticationToken
Issue Type:
Improvement
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2019-03-28 18:19
Priority:
Major
Reporter:
Nicholas Brown
It would be useful to be able to set the authenticationToken from a credential. As well as keeping it secret if the job dsl description is kept in public source control, the credential can be injected/managed in the credential store using deployment tools (ansible/puppet/chef). The below attempt at a work around using `credentialsBinding` does not work as this not executed as part of the job dsl which which is setting authenticationToken.
pipelineJob('exampleJob') {
displayName("Example Job")
wrappers {
credentialsBinding {
string ('AUTH_TOKEN', 'secret_exampleJob_auth_token')
}
}
definition {
cpsScm {
scm {
git {
remote {
url('ssh://g...@example.com/user/example.git')
credentials('git_ssh_private_key_credential')
}
branch('*/master')
}
scriptPath('Jenkinsfile')
}
}
}
// DOES NOT WORK AS AUTH_TOKEN NOT AVAILABLE HERE
// WRAPPER ONLY EXECUTED AS PART OF ACTUAL JOB
authenticationToken(AUTH_TOKEN)
}
[JIRA] (JENKINS-43353) Ability to abort all previous running builds
Title: Message Title Nicholas Brown commented on JENKINS-43353 Re: Ability to abort all previous running builds This would form an effective solution for: https://issues.jenkins-ci.org/browse/JENKINS-47503 https://issues.jenkins-ci.org/browse/JENKINS-43132 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-43132) Cancel existing job if the new job is pending
Title: Message Title Nicholas Brown updated an issue Jenkins / JENKINS-43132 Cancel existing job if the new job is pending Change By: Nicholas Brown Component/s: workflow-multibranch-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-43132) Cancel existing job if the new job is pending
Title: Message Title Nicholas Brown updated an issue Jenkins / JENKINS-43132 Cancel existing job if the new job is pending Change By: Nicholas Brown Labels: multi-branch Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date
Title: Message Title Nicholas Brown updated an issue Jenkins / JENKINS-54401 java.lang.NullPointerException when parsing target revision date Change By: Nicholas Brown Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date
Title: Message Title Nicholas Brown commented on JENKINS-54401 Re: java.lang.NullPointerException when parsing target revision date This is the Pull-Request that introduced this code: https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/145 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date
Title: Message Title Nicholas Brown commented on JENKINS-54401 Re: java.lang.NullPointerException when parsing target revision date The NullPointerException exception is in the new file BitbucketGitSCMRevision.java introduced as part of JENKINS-53707 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-47503) Abort ongoing builds of PR if new change to the same PR was submitted
Title: Message Title Nicholas Brown updated an issue Jenkins / JENKINS-47503 Abort ongoing builds of PR if new change to the same PR was submitted Change By: Nicholas Brown Component/s: workflow-multibranch-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-47503) Abort ongoing builds of PR if new change to the same PR was submitted
Title: Message Title Nicholas Brown updated an issue Jenkins / JENKINS-47503 Abort ongoing builds of PR if new change to the same PR was submitted Change By: Nicholas Brown Labels: bitbucket-branch-source-plugin multibranch Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Nicholas Brown commented on JENKINS-32997 Re: Pipeline job: Abort older builds which are running A related issue about cancelling builds on branch updates is here: https://issues.jenkins-ci.org/browse/JENKINS-47503 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-47503) Abort ongoing builds of PR if new change to the same PR was submitted
Title: Message Title Nicholas Brown commented on JENKINS-47503 Re: Abort ongoing builds of PR if new change to the same PR was submitted Related context: The GitHub build plugin provides a feature for this:https://github.com/jenkinsci/ghprb-plugin/issues/411 A similar question was asked here: https://issues.jenkins-ci.org/browse/JENKINS-32997 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-47503) Abort ongoing builds of PR if new change to the same PR was submitted
Title: Message Title Nicholas Brown commented on JENKINS-47503 Re: Abort ongoing builds of PR if new change to the same PR was submitted This looks like it might be a work around: https://stackoverflow.com/a/48956042 But I agree there should be a builtin pipeline option for this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49471) Add option for suppressing notifications to Bitbucket
Title: Message Title Nicholas Brown commented on JENKINS-49471 Re: Add option for suppressing notifications to Bitbucket Possible duplicate of #49216 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-34981) Make valgrind-plugin compatible with pipeline
Title: Message Title Nicholas Brown commented on JENKINS-34981 Re: Make valgrind-plugin compatible with pipeline Is there a simply Declarative Pipeline syntax for this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-45997) BitBucket PRs failing to checkout on initial run after PR updated with new commits
Title: Message Title
Nicholas Brown commented on JENKINS-45997
Re: BitBucket PRs failing to checkout on initial run after PR updated with new commits
I think Justin Wojciechowski solution of having the Bitbucket Branch Source Plugin hit the CanMerge Rest API, to force the branch creations, is a good one. It need not even be a configuration option, Bitbucket Branch Source Plugin should simply do this every time it discovers PRs. In a some older Jenkins jobs I had, not making use of Bitbucket Branch Source Plugin, I had the same issue and used this horrid work around:
# Nasty hack to force Stash to generate the /merge branch for the PR
set +x
curl -u ${STASH_USER}:${STASH_PASSWORD} ${STASH_URL}/rest/api/1.0/projects/${destinationRepositoryOwner}/repos/${destinationRepositoryName}/pull-requests/${pullRequestId}/diff > /dev/null
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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] (JENKINS-41218) Provide native systemd unit
Title: Message Title Nicholas Brown created an issue Jenkins / JENKINS-41218 Provide native systemd unit Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: packaging Created: 2017/Jan/19 3:16 PM Priority: Minor Reporter: Nicholas Brown Currently debian packages (and presumably redhat/suse/etc) ship with old style SysV init.d file. Most distributions are now systemd based, and to be able to make use of it's additional features it would be useful have /lib/systemd/system/jenkins.service file. This would allow features like systemd's restart functionality to work (useful when Jenkins occasionally crashes, etc). See discussion around this here: http://serverfault.com/questions/760552/how-to-use-automatic-restart-with-jenkins-on-systemd Details of how provide both systemd unit file and SysV init file are detailed here: https://wiki.debian.org/Teams/pkg-systemd/Packaging This should be applicable to all distro, and systemd unit most likely the same across them all, as it's much more standardised than each distros SysV init infrastructure. https://github.com/jenkinsci/packaging Add Comment
[JIRA] (JENKINS-35156) valgrind plugin crashes
Title: Message Title Nicholas Brown commented on JENKINS-35156 Re: valgrind plugin crashes Johannes Ohlemacher did you get a chance to look into this? I'm consistently seeing this with every use of plugin I make. I'm using 0.27 of the plugin with Jenkins 2.7.4 on Debian Jessie 64 bit using 1.7.0_101 of OpenJDK, and the config I mentioned before. Are there further debugs I can collect to help? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33917) Add support for token-macro plugin
Title: Message Title Nicholas Brown updated an issue Jenkins / JENKINS-33917 Add support for token-macro plugin Change By: Nicholas Brown Labels: macro Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-28831) Global Stash configuration + Jenkins credentials
Title: Message Title Nicholas Brown resolved as Fixed This was fixed by https://github.com/nemccarthy/stash-pullrequest-builder-plugin/pull/61 Jenkins / JENKINS-28831 Global Stash configuration + Jenkins credentials Change By: Nicholas Brown Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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,
[JIRA] (JENKINS-29274) Comment log checker does not handle build names with regex special characters
Title: Message Title Nicholas Brown resolved as Fixed https://github.com/jenkinsci/stash-pullrequest-builder-plugin/pull/17 has been merged and a release made. Jenkins / JENKINS-29274 Comment log checker does not handle build names with regex special characters Change By: Nicholas Brown Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-32655) Add support for Pipeline job types
Title: Message Title Nicholas Brown updated an issue Jenkins / JENKINS-32655 Add support for Pipeline job types Change By: Nicholas Brown Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37468) Support for ssh keys in Stash Pull Request Plugin
Title: Message Title Nicholas Brown closed an issue as Won't Fix This requires upstream Stash to support ssh keys, there is nothing the Jenkins plugin can do about this. Jenkins / JENKINS-37468 Support for ssh keys in Stash Pull Request Plugin Change By: Nicholas Brown Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-37468) Support for ssh keys in Stash Pull Request Plugin
Title: Message Title Nicholas Brown commented on JENKINS-37468 Re: Support for ssh keys in Stash Pull Request Plugin https://github.com/jenkinsci/stash-pullrequest-builder-plugin/pull/18 has been merged, that should block selecting ssh keys as Stash does not support them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37551) No build parameters are getting set after upgrading to Jenkins 2.7
Title: Message Title Nicholas Brown closed an issue as Duplicate Jenkins / JENKINS-37551 No build parameters are getting set after upgrading to Jenkins 2.7 Change By: Nicholas Brown Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-34847) Missing parameters
Title: Message Title Nicholas Brown resolved as Fixed Fixed in https://github.com/nemccarthy/stash-pullrequest-builder-plugin/pull/89 Jenkins / JENKINS-34847 Missing parameters Change By: Nicholas Brown Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-34847) Missing parameters
Title: Message Title Nicholas Brown updated an issue Jenkins / JENKINS-34847 Missing parameters Change By: Nicholas Brown Comment: Fixed by https://github.com/nemccarthy/stash-pullrequest-builder-plugin/pull/89 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-34847) Missing parameters
Title: Message Title Nicholas Brown commented on JENKINS-34847 Re: Missing parameters Fixed by https://github.com/nemccarthy/stash-pullrequest-builder-plugin/pull/89 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-34931) Build merge commit instead of PR head
Title: Message Title Nicholas Brown commented on JENKINS-34931 Re: Build merge commit instead of PR head Is this a duplicate of JENKINS-36283 ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [cppcheck-plugin] (JENKINS-35096) Add support for Jenkins Pipeline to the cppcheck-plugin
Title: Message Title Nicholas Brown commented on JENKINS-35096 Re: Add support for Jenkins Pipeline to the cppcheck-plugin I think what's needed is to implement the `SimpleBuildStep` class interface. similar to what the xunit plugin does: https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java#L63 cppcheck does not implement this: https://github.com/jenkinsci/cppcheck-plugin/blob/master/src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckPublisher.java#L32 See also: https://github.com/jenkinsci/cobertura-plugin/issues/50 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] [sloccount-plugin] (JENKINS-35234) Support the new workflow/pipeline model
Title: Message Title Nicholas Brown updated an issue Jenkins / JENKINS-35234 Support the new workflow/pipeline model Change By: Nicholas Brown Labels: pipeline 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] [sloccount-plugin] (JENKINS-35234) Support the new workflow/pipeline model
Title: Message Title Nicholas Brown created an issue Jenkins / JENKINS-35234 Support the new workflow/pipeline model Issue Type: Improvement Assignee: npiguet Components: sloccount-plugin Created: 2016/May/31 1:10 PM Priority: Major Reporter: Nicholas Brown Pipeline jobs appears to be the standard interface for Jenkins 2.0 and forward. I think it requires implementing the 'SimpleBuildStep' class interface. Similar issue with many other publisher plugins, eg: https://github.com/jenkinsci/cobertura-plugin/issues/50#issuecomment-222680913 Add Comment
[JIRA] [valgrind-plugin] (JENKINS-35156) valgrind plugin crashes
Title: Message Title Nicholas Brown commented on JENKINS-35156 Re: valgrind plugin crashes I'm using version 0.27 of the plugin with Jenkins 2.2 on Debian Jessie 64 bit using 1.7.0_101 of OpenJDK. The plugin has a relatively vanilla config: Executable include path: */tests/functional/binary_ Executable arguments: -d0 Working directory: obj-x86_64-linux-gnu/ Output directory: obj-x86_64-linux-gnu/ file ending: .valgrind_results leak check level: full Remove old reports: Yes trace children: Yes 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] [valgrind-plugin] (JENKINS-35156) valgrind plugin crashes
Title: Message Title Nicholas Brown created an issue Jenkins / JENKINS-35156 valgrind plugin crashes Issue Type: Bug Assignee: Johannes Ohlemacher Components: valgrind-plugin Created: 2016/May/26 4:39 PM Environment: 0.27 of the Valgrind Plugin 2.2 of Jenkins Priority: Major Reporter: Nicholas Brown My logs contain: 17:22:50 $ valgrind --version 17:22:50 [Valgrind] detected valgrind version (valgrind): 3.11.0 17:22:50 [Valgrind] includes files: binary_foo, binary_bar 17:22:50 [Valgrind] ERROR, java.lang.NullPointerException: null 17:22:50 Build step 'Run Valgrind' marked build as failure I'm using version 0.27 of the plugin, and Jenkins 2.2. Are there any steps to further debug what is causing this crash?
[JIRA] [stash-pullrequest-builder-plugin] (JENKINS-34847) Missing parameters
Title: Message Title Nicholas Brown created an issue Jenkins / JENKINS-34847 Missing parameters Issue Type: Bug Assignee: nathan m Components: stash-pullrequest-builder-plugin Created: 2016/May/16 9:48 AM Labels: security-170 Priority: Blocker Reporter: Nicholas Brown The fix for SECURITY-170 as described in this blog post means that Jenkins core filters out any parameters used that were not defined in the job: https://jenkins.io/blog/2016/05/11/security-update/ Since Stash Pullrequest builder defines lots of parameters at runtime, and then later tries to access them, a bunch of functionality in the plugin fails. See an example resulting failure at https://github.com/nemccarthy/stash-pullrequest-builder-plugin/issues/84 Presumably this plugin should define its own Action class to store this information, rather than relying on these parameters to be exported into the environment during a build. This similar to issue seen in GHPRB plugin.
[JIRA] [stash-pullrequest-builder-plugin] (JENKINS-28831) Global Stash configuration + Jenkins credentials
Title: Message Title Nicholas Brown commented on JENKINS-28831 Re: Global Stash configuration + Jenkins credentials I think this was resolved by https://github.com/nemccarthy/stash-pullrequest-builder-plugin/pull/61 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] [stash-pullrequest-builder-plugin] (JENKINS-32655) Add support for Pipeline job types
Title: Message Title Nicholas Brown commented on JENKINS-32655 Re: Add support for Pipeline job types See https://github.com/nemccarthy/stash-pullrequest-builder-plugin/issues/80 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-34762) PR status cannot be updated due to filtered parameters
Title: Message Title Nicholas Brown commented on JENKINS-34762 Re: PR status cannot be updated due to filtered parameters https://github.com/nemccarthy/stash-pullrequest-builder-plugin/issues/84 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-34762) PR status cannot be updated due to filtered parameters
Title: Message Title Nicholas Brown commented on JENKINS-34762 Re: PR status cannot be updated due to filtered parameters I'd guess that https://github.com/jenkinsci/stash-pullrequest-builder-plugin may have the same problem as it appears define extra parameters in a similar way. 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] [bitbucket-branch-source-plugin] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications
Title: Message Title Nicholas Brown commented on JENKINS-33507 Re: Bitbucket Server webhooks and Bitbucket Cloud build status notifications I'm guessing that Bitbucket server auto-register webhook support is not yet implemented, despite the option being presented in the Branch source configuration? https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/f50ce24f4afc75e6dae00c44ea20b8fa137bd72d/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/hooks/WebhookAutoRegisterListener.java#L187 If I enable this option when configuring Jenkins with my Bitbucket Server details and visit http:// [JENKINS_ROOT_URL]/bitbucket-scmsource-hook/notify I get the below error in my browser. Until this implemented, could the help-autoRegisterHooks.jelly perhaps be updated to point out BitBucket Server is not supported. I think this means that automatic branch re-indexing of branches will also not happen as this based off SCM change notification, and thus, 'Periodically if not otherwise run' Build Trigger will need to configured so that this happens. java.lang.Exception: X-Event-Key HTTP header not found at org.kohsuke.stapler.HttpResponses.error(HttpResponses.java:83) at com.cloudbees.jenkins.plugins.bitbucket.hooks.BitbucketSCMSourcePushHookReceiver.doNotify(BitbucketSCMSourcePushHookReceiver.java:68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-33841) Support for pipeline builds
Title: Message Title Nicholas Brown commented on JENKINS-33841 Re: Support for pipeline builds Perhaps some overlaps with this? https://github.com/jenkinsci/stashnotifier-plugin/issues/92 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-branch-source-plugin] (JENKINS-33161) Allow merge commits to be built from origin PRs
Title: Message Title Nicholas Brown commented on JENKINS-33161 Re: Allow merge commits to be built from origin PRs It would be great to see this also added to the bitbucket-branch-source plugin. 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] [valgrind-plugin] (JENKINS-34643) New release
Title: Message Title Nicholas Brown created an issue Jenkins / JENKINS-34643 New release Issue Type: Task Assignee: Johannes Ohlemacher Components: valgrind-plugin Created: 2016/May/06 1:24 PM Priority: Minor Reporter: Nicholas Brown There's not been a release in more than year, but there have been quite a few commits since then: https://github.com/jenkinsci/valgrind-plugin/compare/valgrind-0.26...master https://github.com/jenkinsci/valgrind-plugin/compare/valgrind-0.25b...master Add Comment
[JIRA] [ircbot] (JENKINS-24507) Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled
Nicholas Brown commented on JENKINS-24507 Publisher hudson.plugins.ircbot.IrcPublisher aborts due to exception when reporting on tests is enabled Perhaps related to JENKINS-24413 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
