[JIRA] (JENKINS-60839) Use the new PipelineAPI to correctly mark the right stage as unstable if tests fail
Title: Message Title Roman Bäriswyl commented on JENKINS-60839 Re: Use the new PipelineAPI to correctly mark the right stage as unstable if tests fail I could probably do it myself and open a PR but I miss some more background. The biggest problem is that in nunit-plugin at the specific place, I only see a `build (Run)` object. And it is based on `SimpleBuildStep` where I do not see the `getContext` method to get the `node` where I should add the `addOrReplaceAction(new WarningAction(Result.UNSTABLE)`. If someone could give me some hints, I could create a PR myself for this. 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.204194.1579701404000.3848.1579703580047%40Atlassian.JIRA.
[JIRA] (JENKINS-60839) Use the new PipelineAPI to correctly mark the right stage as unstable if tests fail
Title: Message Title Roman Bäriswyl created an issue Jenkins / JENKINS-60839 Use the new PipelineAPI to correctly mark the right stage as unstable if tests fail Issue Type: Improvement Assignee: Unassigned Components: nunit-plugin Created: 2020-01-22 13:56 Priority: Major Reporter: Roman Bäriswyl Currently, when any of the tests fail, the whole build is marked as unstable without further incofmation (happens probably here) Now that there is a new API which passes more information about the failed step. That change is documented here. So the nunit plugin should be adjusted so that it can be displayed, where the build got unstable. In JUnit, this PR introduced this change. This PR might be used as idea on how to implement this. Add Comment
[JIRA] (JENKINS-58420) Column shows "-" on failed builds
Title: Message Title Roman Baeriswyl created an issue Jenkins / JENKINS-58420 Column shows "-" on failed builds Issue Type: Bug Assignee: Ulli Hafner Attachments: image.png Components: warnings-ng-plugin Created: 2019-07-10 09:22 Environment: Jenkins 2.184, Docker (Linux) Priority: Minor Reporter: Roman Baeriswyl The column Number of static analysis issues shows only a - when a build fails. In the job details, issues are visible correctly. Changing enabledForFailure to true and ignoreFailedBuilds to false does not change this behavior. Add Comment
[JIRA] (JENKINS-40518) Give the unzip step a parameter to suppress verbose output
Title: Message Title Roman Baeriswyl commented on JENKINS-40518 Re: Give the unzip step a parameter to suppress verbose output Seems to be released: https://github.com/jenkinsci/pipeline-utility-steps-plugin/blob/master/CHANGES.md 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-42578) Parameters (from Properties) should have an option to keep the previous value
Title: Message Title
Roman Baeriswyl updated an issue
Jenkins / JENKINS-42578
Parameters (from Properties) should have an option to keep the previous value
Change By:
Roman Baeriswyl
To define parameters in a pipeline script (especially multi-branch), you need to use the properties step and define the parameters there.Unfortunately, the defaultValue defined there will always overwrite the value which might have been adjusted in the Jenkins Web UI.I currently use the following to keep the values:{code:java}properties([// Parametersparameters([string(name: 'buildType', defaultValue: (params.buildType == null) ? 'Release' : params.buildType, description: 'Defines which build should be run (Release / Debug)'),booleanParam(name: 'runUnitTests', defaultValue: (params.runUnitTests == null) ? true : params.runUnitTests, description: 'Defines if unit tests should be run')])]){code}As you see, in each defaulValue defaultValue I first check if it is not null and if so, use the previous value and only otherwise use the defaultValue.Would be great to either have the defaultValue to behave like this by default or have a flag: defaultOnlyIfNotSet or something like that.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42578) Parameters (from Properties) should have an option to keep the previous value
Title: Message Title
Roman Baeriswyl updated an issue
Jenkins / JENKINS-42578
Parameters (from Properties) should have an option to keep the previous value
Change By:
Roman Baeriswyl
To define parameters in a pipeline script (especially multibranch multi-branch ), you need to use the properties step and define the parameters there.Unfortunately, the defaultValue defined there will always overwrite the value which might be have been adjusted in the Jenkins Web UI.I currently use the following to keep the values:{code:java}properties([// Parametersparameters([string(name: 'buildType', defaultValue: (params.buildType == null) ? 'Release' : params.buildType, description: 'Defines which build should be run (Release / Debug)'),booleanParam(name: 'runUnitTests', defaultValue: (params.runUnitTests == null) ? true : params.runUnitTests, description: 'Defines if unit tests should be run')])]){code}As you see, in each defaulValue I first check if it is not null and if so, use the previous value and only otherwise use the defaultValue.Would be great to either have the defaultValue to behave like this always by default or have a flag: defaultOnlyIfNotSet or something like that.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42578) Parameters (from Properties) should have an option to keep the previous value
Title: Message Title Roman Baeriswyl created an issue Jenkins / JENKINS-42578 Parameters (from Properties) should have an option to keep the previous value Issue Type: Improvement Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2017/Mar/08 12:40 PM Priority: Minor Reporter: Roman Baeriswyl To define parameters in a pipeline script (especially multibranch), you need to use the properties step and define the parameters there. Unfortunately, the defaultValue defined there will always overwrite the value which might be adjusted in the Jenkins Web UI. I currently use the following to keep the values: properties([ // Parameters parameters([ string(name: 'buildType', defaultValue: (params.buildType == null) ? 'Release' : params.buildType, description: 'Defines which build should be run (Release / Debug)'), booleanParam(name: 'runUnitTests', defaultValue: (params.runUnitTests == null) ? true : params.runUnitTests, description: 'Defines if unit tests should be run') ]) ]) As you see, in each defaulValue I first check if it is not null and if so, use the previous value and only otherwise use the defaultValue. Would be great to either have the defaultValue to behave like this always or have a flag: defaultOnlyIfNotSet or something like that.
[JIRA] (JENKINS-38984) Branch Indexing / Folder Computation fails if branch name contains german umlauts like ü, ö or ä
Title: Message Title Roman Baeriswyl commented on JENKINS-38984 Re: Branch Indexing / Folder Computation fails if branch name contains german umlauts like ü, ö or ä I think a possible fix would be to UrlEncoder.encode the branch variable in checkPathExists (and possibly other places) in BitbucketServerAPIClient.java. Unfortunately I do not have experience with jenkins plugins so I cannot really test this. 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-38984) Branch Indexing / Folder Computation fails if branch name contains german umlauts like ü, ö or ä
Title: Message Title Roman Baeriswyl commented on JENKINS-38984 Re: Branch Indexing / Folder Computation fails if branch name contains german umlauts like ü, ö or ä I'm facing the same issue. Can this be addressed sometime soon? 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-30206) Multibranch plugin: Modified properties do not propagate to existing branches
Title: Message Title Roman Baeriswyl updated an issue Jenkins / JENKINS-30206 Multibranch plugin: Modified properties do not propagate to existing branches Change By: Roman Baeriswyl Comment: Any news on this? How can this be resolved while the problem is not fixed in the plugin? 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-30206) Multibranch plugin: Modified properties do not propagate to existing branches
Title: Message Title Roman Baeriswyl commented on JENKINS-30206 Re: Multibranch plugin: Modified properties do not propagate to existing branches Any news on this? How can this be resolved while the problem is not fixed in the plugin? 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-41661) LTS branch does not contain SCM API 2.0.2 release, but depends on it
Title: Message Title Roman Baeriswyl edited a comment on JENKINS-41661 Re: LTS branch does not contain SCM API 2.0.2 release, but depends on it Thanks [~stensonb]I built it according to your manual and also uploaded it here: http://www.flauschig.ch/transfer/scm-api-2.0.2.hpiNow everything is back to normal. 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-41661) LTS branch does not contain SCM API 2.0.2 release, but depends on it
Title: Message Title Roman Baeriswyl commented on JENKINS-41661 Re: LTS branch does not contain SCM API 2.0.2 release, but depends on it Thanks Bryan Stenson I built it according your manual and also uploaded it here: http://www.flauschig.ch/transfer/scm-api-2.0.2.hpi Now everything is back to normal. 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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build
Title: Message Title Roman Baeriswyl commented on JENKINS-38005 Re: Using archiveArtifacts with a non-matching pattern silently fails the build Same for me. Almost half a day to figure out that this silently fails the build without any warning! 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-32831) "None of the Update Sites passed the signature check" w/ Jenkins v1.647
Title: Message Title Roman Baeriswyl commented on JENKINS-32831 Re: "None of the Update Sites passed the signature check" w/ Jenkins v1.647 Looks like that issue came back. I now get this every time when I try to check for updates with the experimental url. It did work until about 8 hours ago but then stopped working until now. 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-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Roman Baeriswyl edited a comment on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection Very clever solution but unfortunately does not work for git :( Also the BitBucket Branch Source Plugin also does seems not seem to help. Still the The entire branch is still checked out on the master . 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-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Roman Baeriswyl edited a comment on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection Very clever solution but unfortunately does not work for git :( Also the BitBucket Branch Source Plugin also does not seem to help. Still the entire branch is checked out. 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-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Roman Baeriswyl commented on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection Very clever solution but unfortunately does not work for git 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-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Roman Baeriswyl commented on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection Unfortunately I am using (and need) the multibranch-pipeline-plugin. There I do not have any possibilities to define a subfolder or reduce the checkout depth. 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-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Roman Baeriswyl commented on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection Would it be possible to move the Jenkinsfile to a subfolder and then let the jenkins master only checkout this directory? This is quite an issue if you have a jenkins instance for many repositories. 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-37895) Option to "skip" a locked section if a newer build already completed it
Title: Message Title Roman Baeriswyl commented on JENKINS-37895 Re: Option to "skip" a locked section if a newer build already completed it The milestone plugin will be here (I guess): https://github.com/jenkinsci/pipeline-milestone-step-plugin 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-37895) Option to "skip" a locked section if a newer build already completed it
Title: Message Title Roman Baeriswyl commented on JENKINS-37895 Re: Option to "skip" a locked section if a newer build already completed it Just found out that this should be possible to achieve with the milestone step. Hopefully that will get released soon. 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-37895) Option to "skip" a locked section if a newer build already completed it
Title: Message Title Roman Baeriswyl commented on JENKINS-37895 Re: Option to "skip" a locked section if a newer build already completed it Regarding the documentation, the concurrency property of a Stage (which is now deprecated) could exactly do this: The stage command lets you mark certain sections of a build as being constrained by limited concurrency (or, later, unconstrained). Newer builds are always given priority when entering such a throttled stage; older builds will simply exit early if they are preëmpted. This really is now a missing feature for me. 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-37895) Option to "skip" a locked section if a newer build already completed it
Title: Message Title Roman Baeriswyl created an issue Jenkins / JENKINS-37895 Option to "skip" a locked section if a newer build already completed it Issue Type: Improvement Assignee: Unassigned Components: lockable-resources-plugin Created: 2016/Sep/01 2:29 PM Priority: Minor Reporter: Roman Baeriswyl It would be great to have an option that when an older build finally gets a lock it can skip it because a newer build already completed it. Example: Start build 1 Start build 2 build 2 reaches locked block build 1 reaches locked block build 2 executes locked block (eg sonarqube scanner or deployment) build 2 frees the lock build 1 gets the lock build 1 skips block in the lock because a newer build already completed it As far as I understand this cannot be done right now. Would be really handy to have this. Add Comment
