[JIRA] (JENKINS-37297) can't use github deploy keys in Multi-Branch Project Plugin
Title: Message Title liron tal commented on JENKINS-37297 Re: can't use github deploy keys in Multi-Branch Project Plugin I won't be able to test run this PR soon, sorry. 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-37312) BlueOcean "Failed to write numberOfFailingBranches" exception
Title: Message Title Jonathan del Strother commented on JENKINS-37312 Re: BlueOcean "Failed to write numberOfFailingBranches" exception Total stab-in-the-dark, but is it because I have a mixture of pipeline & non-pipeline jobs? (and, for that matter, a mix of multibranch and non-multibranch jobs) 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-37401) trigger release via post build step
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-37401 trigger release via post build step Issue Type: New Feature Assignee: Stanley Hillner Components: unleash-plugin Created: 2016/Aug/14 3:41 PM Priority: Minor Reporter: Jae Gangemi i was wondering if you would consider adding (or accept as a PR) a post build step that would allow one to invoke this plugin when a snapshot build is successful which would allow for a more continuous delivery process. right now the only way to achieve this is to create a separate job that invokes the goals directly which means i need to maintain two build configurations, etc. Add Comment
[JIRA] (JENKINS-37402) Enable project-based security causing job configure page to overflow in right
Title: Message Title Rohit Agarwal created an issue Jenkins / JENKINS-37402 Enable project-based security causing job configure page to overflow in right Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: Page_overflow.jpg Components: matrix-project-plugin Created: 2016/Aug/14 3:58 PM Environment: Jenkins upgraded to 2.7.2 version Matrix Authorization Strategy Plugin version - 1.2 Priority: Critical Reporter: Rohit Agarwal Hi, I upgraded my jenkins from 1.599 version to 2.7.2 and it results in job configuration page overflow to right when i check Enable project based security button. Please help in resolving this as it is my production instance Add Comment
[JIRA] (JENKINS-37397) Allow tool step to use Symbol names instead of classes for tool types
Title: Message Title Andrew Bayer updated JENKINS-37397 Jenkins / JENKINS-37397 Allow tool step to use Symbol names instead of classes for tool types Change By: Andrew Bayer Status: In Progress Review 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-37397) Allow tool step to use Symbol names instead of classes for tool types
Title: Message Title Andrew Bayer started work on JENKINS-37397 Change By: Andrew Bayer Status: Open In Progress 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-37397) Allow tool step to use Symbol names instead of classes for tool types
Title: Message Title Andrew Bayer commented on JENKINS-37397 Re: Allow tool step to use Symbol names instead of classes for tool types PR up at https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/16 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-37397) Allow tool step to use Symbol names instead of classes for tool types
Title: Message Title
Andrew Bayer updated an issue
Jenkins / JENKINS-37397
Allow tool step to use Symbol names instead of classes for tool types
Change By:
Andrew Bayer
Related to JENKINS- 37836 37386 - now that we're getting {{@Symbol}} on {{ToolDescriptor}}, it makes sense to change the {{tool}} step to take either the descriptor ID (i.e., the class name) or the relevant symbol.
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-37391) Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Title: Message Title
Andrew Bayer updated JENKINS-37391
Merged - thanks, Mark Waite!
Jenkins / JENKINS-37391
Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Change By:
Andrew Bayer
Status:
In Review 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 https://groups.google.com/d/optou
[JIRA] (JENKINS-37403) Add a convenience static method for getting @Symbol values off an object
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-37403 Add a convenience static method for getting @Symbol values off an object Issue Type: Improvement Assignee: Andrew Bayer Components: structs-plugin Created: 2016/Aug/14 7:43 PM Priority: Minor Reporter: Andrew Bayer It'd be convenient to have something on SymbolLookup that would take an object, get its class, get the @Symbol annotation on that class if it exists, and either return the value (if it exists and isn't null) or null. I've found myself writing this code in a few places already, so centralizing it seems wise. Add Comment
[JIRA] (JENKINS-37404) Jenkinsfile changes ignored in branch
Title: Message Title
Michael Smith created an issue
Jenkins / JENKINS-37404
Jenkinsfile changes ignored in branch
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
github-organization-folder-plugin
Created:
2016/Aug/14 7:55 PM
Environment:
GitHub Org Folder plugin 1.4 Jenkins 2.17
Priority:
Minor
Reporter:
Michael Smith
I have Jenkins and GitHub configured like this: 1. A GitHub organization with lots of private repos, with very many branches. 2. A GitHub organization webhook with Pull Request, Push and Repository events. (Jenkins' log notes that it received a ping when the hook was set up.) 3. A Jenkins GitHub Organization folder configured to automatically trigger on branches named like .dfiu-devops.. In this org, I have a git repo with no Jenkinsfile in its master branch, but with a Jenkinsfile in a branch named dfiu-devops_earlydays. When Jenkins first scanned the org, it picked up this repo and its branch. However, if I push a change to the Jenkinsfile, Jenkins does not trigger a new build of this job. If I manually trigger a new build, Jenkins does see the latest commit, but builds according to the original pipeline from the first Jenkinsfile commit. It does not update the pipeline with the new Jenkinsfile. My first Jenkinsfile, for testing purposes, looked like this:
#!groovy
stage concurrency: 5, name: 'init'
node('docker') {
step([$class: 'GitHubSetCommitStatusBuilder'])
ws {
pwd()
sh 'pwd; find .'
}
}
Later, I added the shell command en
[JIRA] (JENKINS-37404) Jenkinsfile changes ignored in branch
Title: Message Title
Michael Smith updated an issue
Jenkins / JENKINS-37404
Jenkinsfile changes ignored in branch
Change By:
Michael Smith
I have Jenkins and GitHub configured like this:1. A GitHub organization with lots of private repos, with very many branches.2. A GitHub organization webhook with Pull Request, Push and Repository events. (Jenkins' log notes that it received a ping when the hook was set up.)3. A Jenkins GitHub Organization folder configured to automatically trigger on branches named like {{. \ *dfiu-devops. \ *}}.In this org, I have a git repo with no Jenkinsfile in its {{master}} branch, but with a Jenkinsfile in a branch named {{dfiu-devops_earlydays}}. When Jenkins first scanned the org, it picked up this repo and its branch. However, if I push a change to the Jenkinsfile, Jenkins does not trigger a new build of this job. If I manually trigger a new build, Jenkins _does_ see the latest commit, but builds according to the original pipeline from the first Jenkinsfile commit. It does not update the pipeline with the new Jenkinsfile.My first Jenkinsfile, for testing purposes, looked like this:{code}#!groovystage concurrency: 5, name: 'init'node('docker') { step([$class: 'GitHubSetCommitStatusBuilder']) ws {pwd()sh 'pwd; find .' }}{code}Later, I added the shell command {{env}} inside the `sh` command, but have never seen any change to the output of new builds.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37404) Jenkinsfile changes ignored in branch
Title: Message Title Michael Smith closed an issue as Not A Defect My mistake. I was using an invalid Groovy command in my Jenkinsfile (env). I expected Jenkins to give an error, but instead it just ignored the command, so I thought it was not updating. Jenkins / JENKINS-37404 Jenkinsfile changes ignored in branch Change By: Michael Smith Status: Open Closed Resolution: Not A Defect 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 rece
[JIRA] (JENKINS-37392) Add @Symbol("msbuild") to MSBuild's ToolDescriptor
Title: Message Title Andrew Bayer started work on JENKINS-37392 Change By: Andrew Bayer Status: Open In Progress 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-37392) Add @Symbol("msbuild") to MSBuild's ToolDescriptor
Title: Message Title
Andrew Bayer commented on JENKINS-37392
Re: Add @Symbol("msbuild") to MSBuild's ToolDescriptor
PR up at https://github.com/jenkinsci/msbuild-plugin/pull/27
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-37392) Add @Symbol("msbuild") to MSBuild's ToolDescriptor
Title: Message Title
Andrew Bayer updated JENKINS-37392
Jenkins / JENKINS-37392
Add @Symbol("msbuild") to MSBuild's ToolDescriptor
Change By:
Andrew Bayer
Status:
In Progress Review
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-37405) Ownership Job Filter does not filter non-AbstractProject items
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-37405 Ownership Job Filter does not filter non-AbstractProject items Issue Type: Bug Assignee: Oleg Nenashev Components: ownership-plugin Created: 2016/Aug/14 9:57 PM Environment: ownership-0.8 Priority: Minor Reporter: Oleg Nenashev The implementation of the code in ownership-0.8 ignores all items, which are not instances of Abstract project. It's definitely a bug since the plugin is going to support Pipeline and Folders in the next release. Add Comment
[JIRA] (JENKINS-33400) How to create a log file in the local computer showing only the build status and erros(Jenkins).
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-33400 How to create a log file in the local computer showing only the build status and erros(Jenkins). Change By: Steven Christou Component/s: support-core-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-37379) Some real-time favorite card statuses are not accurate
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37379 Some real-time favorite card statuses are not accurate Change By: James Dumay Sprint: 1.0-pre-beta-1 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-37340) Pipeline jobs fire SSE "job started" events prematurely when classic UI shows the runs as "queued"
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37340 Pipeline jobs fire SSE "job started" events prematurely when classic UI shows the runs as "queued" Change By: James Dumay Priority: Major Blocker Sprint: 1.0-pre-beta-1 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-36582) Developer can see the dashboard update in real time
Title: Message Title James Dumay edited a comment on JENKINS-36582 Re: Developer can see the dashboard update in real time [~cliffmeyers] [~tfennelly] FYI added the linked tickets to the sprint and updated priorities. 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-36582) Developer can see the dashboard update in real time
Title: Message Title James Dumay commented on JENKINS-36582 Re: Developer can see the dashboard update in real time Cliff Meyers FYI added the linked tickets to the sprint and updated priorities. 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-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title James Dumay commented on JENKINS-37323 Re: Ensure that Pipeline Graph can handle stage blocks Vivek Pandey first concern is tracked in JENKINS-35836 - pretty low priority right now. On the second concern, I am not sure. Nested stages seems like a very bad idea - I haven't heard of a good case for it yet. Michael Neale will follow up. 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-26107) Labeled block
Title: Message Title Michael Neale commented on JENKINS-26107 Re: Labeled block Can labelled blocks be nested? if so, why? What is the concrete use case for this? (if they are allowed, it has made things more complicated than they were before, when there were no block scoping). cc Andrew Bayer 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-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title James Dumay commented on JENKINS-37323 Re: Ensure that Pipeline Graph can handle stage blocks Vivek Pandey for the moment can we ensure that block scoped stages work the same way as regular stages, except for the cases you described above? 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-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title James Dumay edited a comment on JENKINS-37323 Re: Ensure that Pipeline Graph can handle stage blocks [~vivek] for the moment can we ensure that block scoped stages work the same way as regular stages, except for the edge cases you described above? 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-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title Michael Neale commented on JENKINS-37323 Re: Ensure that Pipeline Graph can handle stage blocks I am very keen on labelled block stages to NOT be nestable as I don't see why they should be. 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-37340) Pipeline jobs fire SSE "job started" events prematurely when classic UI shows the runs as "queued"
Title: Message Title James Dumay assigned an issue to Tom FENNELLY Jenkins / JENKINS-37340 Pipeline jobs fire SSE "job started" events prematurely when classic UI shows the runs as "queued" Change By: James Dumay Assignee: Tom FENNELLY 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-37104) Ensure matrix projects do not break blue ocean
Title: Message Title Michael Neale commented on JENKINS-37104 Re: Ensure matrix projects do not break blue ocean Vivek Pandey is this still a WIP? hard to tell from state of the ticket 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-33045) Branch Project/Jobs get erased
Title: Message Title Ben Fortuna commented on JENKINS-33045 Re: Branch Project/Jobs get erased Hi, is this confirmed to be resolved, as I am still seeing branch/pull request jobs being deleted intermittently. Is it possibly the same patch to fix JENKINS-34776 needs to be applied elsewhere? 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-37104) Ensure matrix projects do not break blue ocean
Title: Message Title Vivek Pandey stopped work on JENKINS-37104 Change By: Vivek Pandey Resolution: Duplicate Status: In Progress Open 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-37104) Ensure matrix projects do not break blue ocean
Title: Message Title Vivek Pandey commented on JENKINS-37104 Re: Ensure matrix projects do not break blue ocean not being worked on. 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-37104) Ensure matrix projects do not break blue ocean
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37104 Ensure matrix projects do not break blue ocean Change By: Michael Neale 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-37104) Ensure matrix projects do not break blue ocean
Title: Message Title Michael Neale commented on JENKINS-37104 Re: Ensure matrix projects do not break blue ocean Vivek Pandey ok - I think this is probably needed for a version of a beta right?, as many people will try it and it it falls over if they happen to have a matrix job isn't a good look. This may end up being a similar issue to #JENKINS-36980 - do you think? 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-37202) Turn on paging by default
Title: Message Title Michael Neale commented on JENKINS-37202 Re: Turn on paging by default Don't turn this on until Keith's rework is done 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-30412) Access to build's own changelog from script
Title: Message Title James Dumay edited a comment on JENKINS-30412 Re: Access to build's own changelog from script [~jglick] / [~hrmpw] / [~abayer] is there any reason why the change log is sandboxed? Could we offer it in some other way? e.g. request it as a JSON blob or well known array structure ? 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-30412) Access to build's own changelog from script
Title: Message Title James Dumay commented on JENKINS-30412 Re: Access to build's own changelog from script Jesse Glick / Patrick Wolf / Andrew Bayer is there any reason why the change log is sandboxed? Could we offer it in some other way? e.g. request it as a JSON blob or well known array? 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-37400) Symbols for constants variables in workflow-cps
Title: Message Title ikedam commented on JENKINS-37400 Re: Symbols for constants variables in workflow-cps I found script-security calls receiver.getProperty if it's whitelisted. 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-37401) trigger release via post build step
Title: Message Title Stanley Hillner commented on JENKINS-37401 Re: trigger release via post build step Sure, Sounds interesting. If you want to implement this I would wait for a PR. 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-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-37369 Multibranch Pipeline: Last build information is not propagated to Jenkins View Change By: Sverre Moe Attachment: jenkinspipeline1.png 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-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-37369 Multibranch Pipeline: Last build information is not propagated to Jenkins View Change By: Sverre Moe Attachment: jenkinspipeline2.png 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-37406) Multibranch Pipeline: Show SCM Change instead of Branch Indexing
Title: Message Title Sverre Moe created an issue Jenkins / JENKINS-37406 Multibranch Pipeline: Show SCM Change instead of Branch Indexing Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Aug/15 6:40 AM Environment: Jenkins 2.17 workflow-multibranch 2.8 Labels: Pipeline Priority: Minor Reporter: Sverre Moe An SCM Change is no longer depicted in Build History as a badge icon. Instead it shows a Question mark badge icon with the tooltip "Branch indexing". Using Jenkins URL notifyCommit to notify of SCM changes. Want the ++/-- SCM change badge icon to indicate when a build is triggered from an SCM change. Add Comment
[JIRA] (JENKINS-37406) Multibranch Pipeline: Show SCM Change instead of Branch Indexing
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-37406 Multibranch Pipeline: Show SCM Change instead of Branch Indexing Change By: Sverre Moe Attachment: pipelinescmchange1.png 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-37406) Multibranch Pipeline: Show SCM Change instead of Branch Indexing
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-37406 Multibranch Pipeline: Show SCM Change instead of Branch Indexing Change By: Sverre Moe An SCM Change is no longer depicted in Build History as a badge icon.Instead it shows a Question mark badge icon with the tooltip "Branch indexing".Using Jenkins URL notifyCommit to notify of SCM changes. https://jenkins.company.com:8443/git/notifyCommit?url=""> Want the ++/-- SCM change badge icon to indicate when a build is triggered from an SCM change. 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-37406) Multibranch Pipeline: Show SCM Change instead of Branch Indexing
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-37406 Multibranch Pipeline: Show SCM Change instead of Branch Indexing Change By: Sverre Moe An SCM Change is no longer depicted in Build History as a badge icon.Instead it shows a Question mark badge icon with the tooltip "Branch indexing".Using Jenkins URL notifyCommit to notify of SCM changes.https://jenkins.company.com:8443/git/notifyCommit?url=""> .git Want the ++/-- SCM change badge icon to indicate when a build is triggered from an SCM change. 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.
