[JIRA] (JENKINS-46325) Should we use result or currentResult?
Title: Message Title Ethan Spoelstra commented on JENKINS-46325 Re: Should we use result or currentResult? According to the documentation if you are using Scripted Pipeline syntax you probably need to explicitly set the currentBuild.result so that you and Jenkins can track it between stages. https://support.cloudbees.com/hc/en-us/articles/218554077-How-to-set-current-build-result-in-Pipeline- 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-54141) After downgrading a plugin the status page doesn't indicate "Pending restart"
Title: Message Title Ethan Spoelstra created an issue Jenkins / JENKINS-54141 After downgrading a plugin the status page doesn't indicate "Pending restart" Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-10-18 02:56 Environment: Jenkins 2.146 upgraded to 2.147 Java 1.8.0_b181 Ubuntu 14.04 x86_64 Priority: Minor Reporter: Ethan Spoelstra While testing some scripts to automate collecting updated plugins and their versions for our configuration management I wanted to make sure the scripts were idempotent or at least consistent in upgrading everything with an available update that wasn't pinned. To do so I performed a manual downgrade of several plugins through the UI (they were updated from the initial config managed versions by my script) but noticed that on the /updateCenter page I was brought to after clicking 'Downgrade' that the status after downgrading was "Success", with no mention of the restart that IS required to make the downgrade(s) actually take effect. I tested downgrading a couple other plugins with the same result. Navigating to the /pluginManager page I saw that it did have a note at the bottom that an operation was 'awaiting restart' but going to the "pending operations" aka /updateCenter page it simply showed the "Success" status and still no suggestion that the restart was required though the checkbox to restart when no jobs were running was present and usable.
[JIRA] (JENKINS-4816) Allow for grepping console output
Title: Message Title Ethan Spoelstra commented on JENKINS-4816 Re: Allow for grepping console output Dallas Clement The email-ext plugin allows you to select a portion of the failed build log to include in an email, and you can also attach the entire log if you so desire. One thing to note is that adding colorized output via the Ansi colors plugin can greatly expand the size of your logs vs uncolored, so if you have that turned on you may not be able to attach complete logs without using the "compress and attach build.log" option. 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-37500) scm-syn-configuration issues with multi branch project
Title: Message Title Ethan Spoelstra commented on JENKINS-37500 Re: scm-syn-configuration issues with multi branch project I can confirm the hpi built by James Hogarth resolved this issue on one of our instances where we had been testing a multibranch job configuration via Bitbucket source. https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/49#issuecomment-273456696 The change has been merged, there just needs to be a release with the new functionality. 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-46946) Use the bitbucket server webhook api
Title: Message Title Ethan Spoelstra commented on JENKINS-46946 Re: Use the bitbucket server webhook api I would love to see this implemented. Having backwards compatibility or even just multiple method signatures that allows using the old behavior when an extra field like BitbucketType isn't present, would be sweet. The new smart parsing fuctionality looks fantastic and I really hate having to purchase a plugin on the Bitbucket side to send "dumbed down" webhooks to Jenkins if the existing Jenkins built in could handle the newer BB 5.4.x and higher payloads itself. 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-41269) Allow for multiple Octopus Deploy servers similar to Artifactory plugin
Title: Message Title Ethan Spoelstra created an issue Jenkins / JENKINS-41269 Allow for multiple Octopus Deploy servers similar to Artifactory plugin Issue Type: Improvement Assignee: Brian Adriance Components: octopusdeploy-plugin Created: 2017/Jan/20 9:54 PM Labels: configuration Priority: Major Reporter: Ethan Spoelstra We utilize multiple Octopus Deploy "instances" to logically separate our lines of business, but we currently utilize a single build server with appropriate permissions to keep the various lines of business users and jobs separate. Our current CI solution allows us to define an Octopus Deploy instance and API key within the build steps, this allows a lot more flexibility than having a single global configuration, at the expense of a lot of repeated definitions. It would be great to have the best of both worlds with a multi-server global config that allows selecting the appropriate server per job configuration or Octopus Deploy step so we can deploy this via the Job DSL. Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-16360) Print DSL formatted config.xml for an existing Job
Title: Message Title Ethan Spoelstra commented on JENKINS-16360 Re: Print DSL formatted config.xml for an existing Job Christian Bremer It appears someone recently submitted a solution for this (after it expired). Is there code working or have you not had a chance to check? 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] [artifactory-plugin] (JENKINS-25260) Artifact and Artifact checksum deploy order required otherwise artifactory Error 404
Title: Message Title Ethan Spoelstra commented on JENKINS-25260 Re: Artifact and Artifact checksum deploy order required otherwise artifactory Error 404 It is possible to specify the artifact's checksums while uploading rather than adding an additional file. Artifactory will automatically create the file on your behalf if you supply a checksum while uploading or use the Artifactory 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] [artifactory-plugin] (JENKINS-25260) Artifact and Artifact checksum deploy order required otherwise artifactory Error 404
Title: Message Title Ethan Spoelstra edited a comment on JENKINS-25260 Re: Artifact and Artifact checksum deploy order required otherwise artifactory Error 404 It is possible to specify the artifact's checksums while uploading rather than adding an additional file. Artifactory will should automatically create the file checksum files on your behalf if you supply a checksum while uploading or use the Artifactory 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.
