Autofill problem with ActiveDirectory plugin
I'm experiencing the same issue that was supposed to be resolved by https://issues.jenkins-ci.org/browse/JENKINS-29280 Our environment is Jenkins 2.32.3 on CentOS ActiveDirectory plugin 2.3 Chrome browser ver 56.0.2924.87 The workaround is to manually edit the username in config.xml and restart Jenkins. Can someone verify this? If so, then this is a regression. Thank you. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a15591f1-24cd-47f3-9732-7a36ca7b45a9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Parallel in Declarative Pipeline
What's declarative syntax? On Wednesday, February 15, 2017 at 11:48:22 AM UTC-8, pbeatty wrote: > > Is "parallel" valid to use in declarative Jenkinfile syntax or is it only > availabl Scripting syntax? > > Pat > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ee557cf4-7bb9-4fbd-85d9-38653cffeed2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Reset build ID
Is it possible to reset the build ID? I believe there's a plugin to increase the build ID, but not to reset it to a lower number. It might be a useful feature to be reset it when starting a new release of a product. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/beef2daf-731e-4f12-a597-54ec63b641fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Any pointers on docs for using Jenkins to control remote jobs on various machines, non-java.
Pipelines really help in coordinating multiple tasks to be run on multiple
hosts, sequentially and even concurrently. Have you considered this? The
old Jenkins way of define multijobs would be cumbersome so I suggest
looking into pipelines. Another option is something like ansible, though in
practice Jenkins fits the model of CI better.
T
On Tuesday, January 31, 2017 at 4:07:07 PM UTC-8, Rusty Carruth wrote:
>
> So, I'm just looking at Jenkins as a 'controller' for our test scripts.
> I've tried to find some kind of pointers to how to do this, and I do have a
> few ideas, but was hoping I could find some documentation on setting up
> things as below, (yes, I know that I can use ssh or the server on the test
> host (defined below) to start jobs - indeed I've done that, but the more
> important thing is
>
> First, the environment/current process:
>
> We have a Windows-based build machine, 15 linux/FreeDOS-based test hosts,
> a linux-only test host, a linux/Windows test host, and a linux-only OakGate
> test host.
>
> Every day (or more often) a build is run on the windows-based build
> machine.
>
> When the build is finished, the 'products' of the build are placed in a
> new directory on a Linux machine (for now, we'll call it 'client').
>
> Cron jobs are running which detect this and initiate an arbitrary number
> of tests on up to 17 (more or less) of the above 'test hosts'. This is
> done via a (bash) shell script, using a configuration file that can specify
> the configuration file for each test host (the configuration file for each
> test host could be different per host, or all the same, or whatever). This
> startup script does many things, including commanding the serial port
> programs (a modified minicom) running on any one of a number of machines to
> begin saving serial port data to a log file (among other things that the
> bash script can and does do).
>
> This startup bash shell script will initiate (via ssh) a command on each
> test host (as configured above) to begin the test. The host(s) will then
> proceed with the test, as configured, until the test ends.
>
> At the time the test ends, a script will be run on the Linux-booted test
> host to upload results back to the initial linux machine ('client', above)
> and create a report (and mail it, and lots of other stuff, including
> database updates, etc).
>
> When booting into Linux, the test host detects that a test was in process
> and checks to see if any 'post-DOS' tests need to be run, and if so runs
> them.
>
> Once all that is done, the test host will then run a script which copies
> the results over to 'client', creates reports, including an email report,
> emails it, updates databases, etc.
>
> Right now, it all works fine. However, as is often the case, we want to
> 'improve' it.
>
> Here's what we want to change to:
>
> The test host must be running Linux before a test is initiated on it
> (trying to use FreeDOS to copy files via the network was a total disaster,
> so we have to do all network operations in Linux)
>
> We plan to allow the test designer to group arbitrary tests together into
> a 'supertest' (the requirement is that they all have to be under the same
> OS) to be run as one.
>
> The test overseer program can then be configured to run any number of
> sequentially-executed invocations of these sets of tests ('supertests'
> above) as the user wants, so that you could run a bunch of Linux tests
> (together in one batch), followed by a bunch of FreeDOS tests (again, as a
> single batch), followed by a bunch of Linux tests, etc.
>
> IF the test host is to run the test under an OS other than Linux, the
> configuration file specified to the initial bash shell script mentioned
> above is used to configure the test. The test host will complete the test
> as specified and then reboot to Linux.
>
> One other 'minor' variation - we can also do a 'manual' run, which
> basically means that the user must cause the Linux host to reboot (at which
> point it will boot into FreeDOS - allowing the user to (using an IPKVM)
> control the test manually if desired). When booting out of FreeDOS it will
> return to Linux, but NOT 'detect that a test was in process' and run
> 'finish').
>
> What we would like to do is remove the 'flowchart' of
> linux/dos/linux/done. We may wish to boot linux/dos/linux/dos/linux/done,
> or perhaps even boot various versions of linux (yeah, not likely, but I had
> to come up with something besides toggling between linux and dos!)
>
> We also want to be able to abort a test group at the first possible moment
> (under FreeDOS the only possible moment is when the tests are finished, of
> course).
>
> Also, we'd like to set some test hosts to repeatedly run tests over and
> over again, regardless of the build machine's finishing. Possibly with
> changes in the test configuration.
>
> Note that there are 18-ish test hosts, with up to 4 or 5 people wanting
Re: Jenkins queuing multiple jobs of same type from SVN post commit hooks, what is expected behaviour?
>From my experience, having multiple pipeline jobs polling for changes causes confusion from the end-user. It seems better to have one "master" job that polls and runs all the other builds. Also it seems Jenkins jobs (including pipeilnes) are quite happy to build concurrently, but I don't know how to handle it yet. So I've selected "Do not allow concurrent builds" in the master pipeline job. As a result, the job will queue. On Tuesday, December 13, 2016 at 9:48:46 PM UTC-8, Christoffer Holmstedt wrote: > > Hi > I'm running a Jenkins server, latest 2.19 LTS release with a few pipeline > jobs. Each job is triggered by a post-commit hook in respective SVN > repository. The problem I have is that I expected Jenkins to only queue up > one similiar job if another job of the same pipeline is already running but > I get one build per commit. > > As an example: Job A is triggered by a post commit from Commit #1. The > build takes 5 minutes so if I commit #2 and #3 to the repository Jenkins > will queue up two more builds, one for each commit. I would expect Jenkins > to only queue one extra build with commit #2 and #3. > > While searching for a solution to this it is not clear what the expected > behaviour is. Jenkins will only queue up one identical build if multiple > remote triggers are actived except in the case if a build uses parameters > in that case if the parameters are different each build will be unique. The > problem here is that I don't use parameterized builds so not sure what is > going on really and what to expect. > > Any help is appreciated. > > Best regards > -- > Christoffer Holmstedt > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9e6d8b89-2566-4bbe-b1ca-02685e2876c6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins queuing multiple jobs of same type from SVN post commit hooks, what is expected behaviour?
Maybe you can configure the 'quiet period'? The default is set in the configuration screen, but you can also set it per job configuration. On Tuesday, December 13, 2016 at 9:48:46 PM UTC-8, Christoffer Holmstedt wrote: > > Hi > I'm running a Jenkins server, latest 2.19 LTS release with a few pipeline > jobs. Each job is triggered by a post-commit hook in respective SVN > repository. The problem I have is that I expected Jenkins to only queue up > one similiar job if another job of the same pipeline is already running but > I get one build per commit. > > As an example: Job A is triggered by a post commit from Commit #1. The > build takes 5 minutes so if I commit #2 and #3 to the repository Jenkins > will queue up two more builds, one for each commit. I would expect Jenkins > to only queue one extra build with commit #2 and #3. > > While searching for a solution to this it is not clear what the expected > behaviour is. Jenkins will only queue up one identical build if multiple > remote triggers are actived except in the case if a build uses parameters > in that case if the parameters are different each build will be unique. The > problem here is that I don't use parameterized builds so not sure what is > going on really and what to expect. > > Any help is appreciated. > > Best regards > -- > Christoffer Holmstedt > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/91be60dd-e5b5-4a93-b59f-2c9dc53a5090%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: using remote api to get the build status upon completion
I find that using the jenkins-cli was the best option to give me the status. https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI On Wednesday, December 14, 2016 at 2:10:25 PM UTC-8, Katta Vijay wrote: > > I was trying to implement jenkins remote api to initiate build and return > the build status upon completion. > > i can able to trigger build by calling GET or POST methods but couldn't > able to receive any response after the build! > > can some one help me here , how to get the status of the build. > > > Thanks > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e1b29b17-e696-44d9-8a2d-c75da12a0695%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
pipeline scm checkout is happening on master node as well as slave node
I configured my Jenkins pipeline job to read my pipeline script from SCM. In my pipeline I do an scm checkout on a slave node. As a result, I have code checked out both on the master node and the slave node, and whenever the Jenkins job is run, it actually reads the pipeline script on the master node, not the slave node. I've just encountered an odd case where the pipeline code on the master was out-of-sync with the latest SCM changes (even though my check-out strategy says to get the latest as much as possible), while the slave had the latest changes but wasn't being used. Maybe this is by design, but what I would really like is an option in the pipeline configuration to checkout the pipeline only on the slave node. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7a4f42be-f9e4-482a-a2ac-543deebf1cfd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Attachments in pipeline notiufication
Is it possible to attach files to notifications sent from a pipeline? I'm interested in using slack or hipchat as documented at https://jenkins.io/blog/2016/07/18/pipline-notifications. I like notifications, but I'm trying to think of a way to let users know about many aspects (artifacts) of our build, not just that the build was "successful" or "failed". -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/279b7033-24a0-43c4-9478-73d530d3b653%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Polling both svn and git from pipeline
Hi, Eventually I ended up building periodically and checking for SCM changee manually in each repository manually. It took some work, but I didn't want to define multiple jobs just for polling. Taro On Tuesday, October 18, 2016 at 2:44:22 PM UTC-7, Rachel Moreno wrote: > > Hi, > > Sorry, it's possible with Pipeline: > > *Polling is supported across multiple SCMs (changes in one or more will > trigger a new build), and again is done according to the SCMs used in the > last build of the pipeline.* > > You'll have to run it once manually for listening to SCM changes. > > More information: > https://github.com/jenkinsci/workflow-scm-step-plugin/blob/master/README.md > > Best regards, > Rachel > > El jueves, 13 de octubre de 2016, 22:56:16 (UTC+2), Rachel escribió: >> >> Hi, >> >> In your case, I would have two separated Jenkins jobs, but sharing the >> same workspace: >> >>- Advanced Project Options > Use custom workspace >> >> I hope be useful. >> >> Best regards, >> Rachel >> >> El miércoles, 12 de octubre de 2016, 2:47:08 (UTC+2), taroc...@gmail.com >> escribió: >>> >>> Is it possible to poll for changes from both svn and git repositories >>> from within a pipeline job? In Jenkins, pipeline scm configuration is tied >>> to a particular scm type (due to a radio button), but I would like to poll >>> both svn and git at the same time. As a result of the poll detecting an scm >>> change, I want to invoke only one build. >>> >>> As a workaround, maybe I need to have two separate Jenkins jobs? >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f0b0a8d-afdd-44f3-9d5e-71d117f392e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Duplicate commits listed in pipeline
Frequently my pipeline build lists duplicate commits in the "Stage View". I just select my job (which is a pipeline) and look at the jobs listed in "Stage View". When I hover over the dark gray box that lists all the commits that went into the build often see duplicate revision numbers. I use the pipeline function Checkout() to do my checkout, and I don't use polling. Is there a update to a plugin that might fix this issue? I'm using Jenkins 2.11 with Pipeline 2.4. Thank you. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8adcb582-6cf1-4f72-bf33-931fd6f15166%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to trigger jenkins job based on result of other job
Perhaps the following snippet is something that you are looking for:
node {
stage('Build') {
build job: 'test-a', propagate: true
build job: 'test-b', propagate: true
}
}
By default propagate is set to true, so this is just to illustrate that you
can ignore errors and failures.
You also need to make sure that in the jobs you invoke (test-a and test-b
in this case) you need to clearly mark successes and failures as such.
node {
currentBuild.result = "SUCCESS"
}
Hope this helps.
On Thursday, November 10, 2016 at 10:17:46 AM UTC-8, pradeep kumar wrote:
>
> Hi All,
>
> I have three jobs (Build, deploy and test ) .Builds job will trigger for
> every one hr and generate the war . then it deploy job will trigger and
> deploy on test env and at last test job will trigger .
> Build-->Deploy-->Test
>
> But i want to trigger the Builds job based on success of Test job . If
> Test job is failure or unstable , my Build should not trigger . Only if
> Test job is success then the Build job has to triggger .
>
> My Build has scheduled for every hr .
>
> Please suggest me .
>
>
> Thanks in advance.
> pradeep
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/28e735d8-f309-4505-b677-8b3010cfc85f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Exposing maven integration test phase to pipeline
I have a pipeline which does a maven build. During the integration test
phase I invoke another Jenkins job.
Is there a way to expose parts of the build process while I'm inside a
Maven build?
// Jenkinsfile
node {
stage(‘Compile’) {
sh ‘mvn clean install’
}
}
// pom.xml
…
org.apache.maven.plugins
maven-antrun-plugin
integration-test
http://localhost:8080/jenkins/ build 'foo' -s" />
run
...
Instead of this:
Stage View:
Compile -> End
I would like to see:
Stage View:
Compile -> Integration Test -> End
And so I would like to somehow communicate to Jenkins, from within the
pom file, that I am in another stage.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/22f2409d-4dc7-475b-918b-d586d199884b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Polling both svn and git from pipeline
Is it possible to poll for changes from both svn and git repositories from within a pipeline job? In Jenkins, pipeline scm configuration is tied to a particular scm type (due to a radio button), but I would like to poll both svn and git at the same time. As a result of the poll detecting an scm change, I want to invoke only one build. As a workaround, maybe I need to have two separate Jenkins jobs? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c409cd54-1467-4896-bb20-7c9a2b064e47%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Pipeline stage view display commits twice
In my pipeline stage view, I aways see two commits even though I have only committed once. I think the problem is because: 1) It is a scheduled job 2) The pipeline itself checks out the code Ideally the schedule would be in the pipeline, but I don't think that's possible. I am using pipeline 2.3. How can I fix this behavior? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0a4a2d45-2ae8-4862-8696-0e23bb420a59%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
pipeline scheduling displays duplicate changes
When I inspect my Jenkins pipeline job, I always see duplicate entries in the Changes view. It may be happening because: i) I have polling enabled, so that the job kicks off if there are any checkins with a time period ii) The pipeline job checks out the code on a build node and does a build Questions: 1) Is there a way to tell Jenkins to only list the changes once? 2) Can the polling schedule somehow be enbedded within the pipeline code? Ideally what I'd like to see is the code polled, checked out, and built on a particular node, but instead what I'm seeing is that the code is checked out on the master and then checked out again on the build node. I'm using Pipeline plugin 2.2 and Jenkins 2.11. Thank you! -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a7caadda-c604-4a0f-80f6-17132faf57fd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
