show defects list pulled from bug tracking system

Hi all, I have need to pull the defects from bug tracking system like HP Quality Center which has REST API exposed. And show those defects in the dashboard view, which will help to track the defects raised or fixed from each build. I tried searching plugin which does this but not finding it.

Re: Changing the upcoming LTS baseline?

That sounds fine with me. I will prepare branch for both 1.636 and 1.642 so we can publish rc as soon as we decide what the baseline will be. -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and

Re: Automatic build and deploy of plugin (CI style)

Hi, As a side note, if you're building out demo machines with a precanned config, there are some really helpful scripts in the Jenkins docker image repo. Even if you're not running docker, the scripts and techniques should work well on demo VMs. To preinstall a list of plugins from the update

Re: Automatic build and deploy of plugin (CI style)

Hi, As a side note, if you're building out demo machines with a precanned config, there are some really helpful scripts in the Jenkins docker image repo. Even if you're not running docker, the scripts and techniques should work well on demo VMs. To preinstall a list of plugins from the update

programmatically changing the labels on a node

I have some groovy code that, under certain conditions, changes the labels on nodes, and I've been having a hard time figuring out exactly how to do it in a way that takes effect right away. I can do something like def slave = Hudson.instance.getSlave("slave-name") slave.labelString = "new

Script Security plugin dry-run for pre-approval?

So I couldn't figure out a good way to word the subject line, but! I've had a few cases where I've needed to go through multiple iterations of "Run a Workflow via a Jenkinsfile" or "Run a system Groovy step", etc, where each time I run, a new method causes the run to fail and is queued up for

Changing the upcoming LTS baseline?

We decided to base the upcoming LTS line on 1.636 in the last meeting on Dec 9. 1.637 introduced two regressions (JENKINS-31458 and JENKINS-31518), that were only resolved in 1.639 and 1.640, so we didn't consider those to be great choices. 1.640 in turn introduced another bug, JENKINS-31954,

Changing the upcoming LTS baseline?

We decided to base the upcoming LTS line on 1.636 in the last meeting on Dec 9. 1.637 introduced two regressions (JENKINS-31458 and JENKINS-31518), that were only resolved in 1.639 and 1.640, so we didn't consider those to be great choices. 1.640 in turn introduced another bug, JENKINS-31954,

Re: Changing the upcoming LTS baseline?

For some reason my original email didn't make it to the list (twice), so reposting as an answer to Oliver's response, hoping this will work. --- We decided to base the upcoming LTS line on 1.636 in the last meeting on Dec 9. 1.637 introduced two regressions (JENKINS-31458 and JENKINS-31518),

Re: Changing the upcoming LTS baseline?

Imho, better wait for some time for 1.642 user testing, then schedule meeting and pick new base (or backport fixes?). Almost all latest LTS's had regressions, rush is not acceptable for "LTS" imho (too much fun with weekly dev builds). On Thursday, December 31, 2015 at 1:46:18 AM UTC+3, Daniel

Re: Changing the upcoming LTS baseline?

> On 31.12.2015, at 00:03, Kanstantsin Shautsou > wrote: > > wait for some time for 1.642 user testing I understand the concern, but I doubt we'll get significantly more testing of a specific version that we have with these two releases already. And we got quite

Re: Changing the upcoming LTS baseline?

> On Dec 31, 2015, at 02:13, Daniel Beck wrote: > > >> On 31.12.2015, at 00:03, Kanstantsin Shautsou >> wrote: >> >> wait for some time for 1.642 user testing > > I understand the concern, but I doubt we'll get significantly more testing of > a

Re: Script Security plugin dry-run for pre-approval?

Hi, I would suggest that you go to https://isues.jenkins-ci.org and file a *New Feature* request, to have a way to test a workflow, and find out up front what all the security problems are with the workflow, without having to execute the workflow. In this post:

Re: Creation of Jenkins slaves and Credentials using the Remote Access API

After some playing around, the following curl command worked for me. Per curl -XPOST 'localhost:8080/credential-store/domain/_/createCredentials' \ --data-urlencode 'json={ "": "0", "credentials": { "scope": "GLOBAL", "id": "",

Re: Remote Jenkins build trigger with authentication, message should be “Started by User XYZ”

Hi All, When I trigger my Jenkins job remotely using URL I use authentication to trigger build like this: wget --auth-no-challenge --http-user=user --http-password=apiToken http://jenkins.yourcompany.com/job/your_job/build?token=TOKEN Build gets triggered without any issue but the

Re: Remote Jenkins build trigger with authentication, message should be “Started by User XYZ”

Hi, wrong ML. Please use the users one, and don't repost the same content. Thanks 2015-12-30 15:37 GMT+01:00 Pritesh Saharey : > > Hi All, > > When I trigger my Jenkins job remotely using URL I use authentication to > trigger build like this: > > wget