Allow a build to be triggered only by a Pipeline
Is there a way to allow users to only build a job as part of an upstream / downstream dependency while disallowing direct execution? 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/e569faa8-3f52-4cc3-8fd5-642ae6f35b99%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Windows Agent As a Service
Thanks! but how do you make it run as a service from the command-line? done of the exes seem to be installed? On Monday, October 15, 2018 at 4:31:03 PM UTC-4, Mark Waite wrote: > > The deprecation of Java Web Start doesn't deprecate the protocols that a > Jenkins agent can use to connect to the Jenkins server. JNLP works just > fine with Java 11 to connect an agent. > > The convenience of clicking the "Web Start" button on the UI won't work > with Java 11, but the command line provided in the agent start page > continues to work. > > Mark Waite > > On Mon, Oct 15, 2018 at 2:18 PM Mark Bidewell > wrote: > >> With Java Web Start deprecated and slated for removal, what is the >> canonical way to create a Windows Service agent? >> >> 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-use...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/439b2186-1f70-46bd-b0f8-c54512eb428b%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/439b2186-1f70-46bd-b0f8-c54512eb428b%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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/06519949-d6f0-49dd-9349-62b56b776e4f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Windows Agent As a Service
With Java Web Start deprecated and slated for removal, what is the canonical way to create a Windows Service agent? 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/439b2186-1f70-46bd-b0f8-c54512eb428b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Migrating to Configuration as Code
Will there be a pathway to migrate from normal Jenkins configuration to Configuration as Code, or will server configuration need to be rewritten from scratch? -- 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/527e2d7f-0ca2-447b-815e-ce8062cdb751%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Rewriting of Config.xml
I recently upgraded my companies Jenkins Server from 2.73.3 to 2.89.4. I also removed some plugins (which I thought did not affect configuration). Upon restarting, My view configuration was largely deleted as well as my globally defined variables. Restoring config.xml from backup and restarting again removed configuration. Has anyone else seen this? -- 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/02392b67-559b-48ee-99bc-5a20f1b84243%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Jenkins Agent Dies on Build Failure
I have a Windows 7 build slave where I am running the java agent using java -jar slave.jar ... There is an Ant build that runs on that slave doing selenium testing. If that Ant build step fails the slave agent immediately dies. If I launch the agent GUI using the Launch button, the agent stays up. Any ideas what is going on? -- 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/20f06146-4084-42be-ad7f-e6f8dfa2835e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Loading scripts from Workflow resources
Thanks, I do #2 right now, but the scripts are in a separate version control. What I would like to do is have the scripts checked out by Jenkins with the external library so that they are auto-updated. Is there a variable or step that gives the path to the location where the library files are checked out? On Tuesday, January 10, 2017 at 10:06:07 AM UTC-5, Ramanathan Muthaiah wrote: > > > > On Tuesday, January 10, 2017 at 7:08:01 PM UTC+5:30, Mark Bidewell wrote: >> >> I am looking at the external libraries capabilities of Jenkins Workflow. >> Our workflow uses python scripts for portions of the build process. Can >> this scripts be stored as resources and a path to them retrieved via >> workflow? Right now the scripts are in a directory on the server not under >> Jenkins control. >> > > Two (actually three) possible options: > > 1) Explore "Managed Scripts" plugin (I suppose this supports only shell > scripts) alongwith Config File Provider plugin. > > 2) If you have Pipeline plugin installed, then these Python scripts can be > invoked using step, "sh" but this will demand your scripts in version > control. > > 3) If the Jenkins job is a freestyle project, then the entire script can > be added as a 'build step' ; but then, every change to the build script > (for bug fixes or new improvements), job needs to be modified and the > script content should be replaced. > > /Ram > -- 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/f0670d45-f022-45e8-8e34-abb47ad8c508%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Loading scripts from Workflow resources
I am looking at the external libraries capabilities of Jenkins Workflow. Our workflow uses python scripts for portions of the build process. Can this scripts be stored as resources and a path to them retrieved via workflow? Right now the scripts are in a directory on the server not under Jenkins control. 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/bcaeecb4-b84b-4ade-a756-144264156c78%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: What is "slave Java"
In short, Jenkins after a certain point Uses Java 1.7+. It appears you are using the Maven project type. This project type injects Jenkins behaviors into the Maven build. These behaviors must run with Java 1.7+. The error you are getting is to to Jenkins attempting to use its behaviors with Java 1.6. In this case the behavior is to run Maven using the JDK on which Jenkins itself is running then set Maven properties for Java to point @ JDK 1.6. Does that help? On Friday, November 18, 2016 at 12:46:48 PM UTC-5, Michael Giroux wrote: > > Thanks Daniel. But I'm still not clear on what is going on under the > covers. The job is NOT configured to run on a slave, but the message > indicates that the build was retried on a slave. Is there a default slave > that runs on the Jenkins host to support this retry? > > On Friday, November 18, 2016 at 8:46:22 AM UTC-7, Daniel Beck wrote: >> >> >> > On 18.11.2016, at 15:46, Michael Giroux wrote: >> > >> > Could someone either explain, or point me to documentation that >> explains what is really happening here? Specifically what does >> > "Retrying with slave Java ..." mean since we do not have a slave named >> "Java". >> >> This refers to the Java runtime used to run the slave (now called build >> agent) process. >> >> -- 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/abe4e308-adce-4955-9f6a-601b701f731d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Email ext to send html body in Pipeline
Support for templates was added in 2.50 if that helps. On Monday, October 10, 2016 at 1:21:28 AM UTC-4, Sam K wrote: > > This works for most part. Except, I have a html formatted file which I > would like to send as the body. Is it possible? Thanks > > emailext attachmentsPattern: '*.log, *.html', body: 'BUILD_URL = ' + > env.BUILD_URL, subject: 'END Coded Pipeline Build SOURCE - ' + CODE_BRANCH > + ' TESTS - ' + TEST_BRANCH, to: MAILING_LIST > -- 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/b2095917-fc69-44b3-85f4-125c27e503f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to limited user to certain jobs
The Role Strategy plugin might be more what you are looking for for Access Control https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin On Wednesday, October 5, 2016 at 5:27:43 AM UTC-4, stanle...@servicemax.com wrote: > > Hello, all > > I am trying to limited some user to access certain jobs, and cannot see > other jobs which are not related to them. > > I am using the "Project-based Matrix Authorization Strategy" to access > control, and it seems I cannot get what I want by this. > Also I try to create user view, but which is not shown by default to that > user too. > > I tried to look at plugins, but it seems I didn't find a proper one. > > Anyone has met the same problem and how did you configure it? > > > Thanks in advance. > > Thanks, > Stanley > > -- 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/bec477c6-4068-4072-8ce5-f40a2c7153ce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Pipeline currentBuild object documention
Is there any documentation on what build properties are exposed by the currentBuild object? 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/bbd3b658-ffc2-4b6a-a973-cf9fee216290%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Using the git command with credentials form a pipeline
I don't know if this helps or not but to use cmd line git in pipeline, I
use the SSH Agent plugin along with SSH key authentication.
On Friday, September 16, 2016 at 4:34:17 PM UTC-4, Nathan Hüsken wrote:
>
> Hi,
>
> I am trying to use git from a pipeline. For this I want to invoke git
> commands using "sh":
>
> sh('git clone https://myserver/project.git')
>
> Some things I want to do require authentication.
>
> When I use the GitSCM plugin (checkout([$class: 'GitSCM', ...), it tells
> me it uses GIT_ASKPASS for credentials.
>
> Can I do that too? How would I have to configure GIT_ASKPASS for this to
> work?
>
> Thanks!
> Nathan
>
--
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/fe2744eb-9f92-4d1b-a7d3-82c022a5f360%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Adding “Perform Maven Release” option from Jenkinsfile
I'm not using a Jenkinsfile, but the solution I arrived at was to have a boolean "Release" build parameter. When checked, this parameter would skip the normal CI SNAPSHOT build and initiate a release. My stages when Source Checkout -> SNAPSHOT Build -> Stage Release -> Release Build The "Stage Release" reads the pom and presents inputs for the build numbers. Does that help? On Wednesday, August 31, 2016 at 3:46:05 PM UTC-4, Harsha Adiga wrote: > > Is there a way to make the Perform Maven Release option visible under the > job created using Jenkinsfile? I have a job that is created manually and it > has this option set by selecting the Maven release build option in > Configure job->Build environment settings. I am trying to convert this > manual job to pipeline job using Jenkinsfile. > -- 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/cebb9d28-93a6-4d86-ac34-6f0c13839281%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
MissingMethodException when Calling Global Libary Functions
I have created a Jira for this but in case anyone else has seen this, I figured I would ask here. I have global functions for certain tasks created using the directions here: https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/README.md They have been working correctly, but after upgrading to the latest pipeline I get the following exception: hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: static Maven.svnRelease() is applicable for argument types: (org.jenkinsci.plugins.workflow.cps.CpsClosure2) values: [org.jenkinsci.plugins.workflow.cps.CpsClosure2@3a07d220] Possible solutions: svnRelease(groovy.lang.Closure) at groovy.lang.MetaClassImpl.invokeStaticMissingMethod(MetaClassImpl.java:1367) at groovy.lang.MetaClassImpl.invokeStaticMethod(MetaClassImpl.java:1353) at org.codehaus.groovy.runtime.callsite.StaticMetaClassSite.call(StaticMetaClassSite.java:50) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:15) at WorkflowScript.run(WorkflowScript:1) at __*cps.transform*__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:55) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:106) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:40) at com.cloudbees.groovy.cps.Next.step(Next.java:58) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:297) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:78) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:206) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:204) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Finished: FAILURE Has anyone else seen this? For Reference the Jira is https://issues.jenkins-ci.org/browse/JENKINS-36673 -- 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/86e2b4d2-ebae-40c6-a485-4452fbd6e57c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Restartable Pipeline stages
Just did. https://issues.jenkins-ci.org/browse/JENKINS-35989 On Tuesday, June 14, 2016 at 11:42:49 PM UTC-4, Rikesh Dhokia wrote: > > I too am looking for functionality like this. @Mark, did you create a > relevant JIRA issue for this? > > > > On Tuesday, 3 May 2016 03:23:07 UTC+10, Mark Bidewell wrote: >> >> Is there a way to implement a restartable stage that could be manually >> restarted? Often in Pipeline examples I see something like: >> >> >>- "Deploy" -> "Deploy Again" ->"Deploy Yet Again" >> >> >> It seems like this could be combined into a single step that could be >> reexecuted. Is this possible? >> > -- 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/03f9d1c0-63ff-4911-988e-51186bb84cf0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Deploy Mule application
What my company wound up doing was creating an internal application that used the MMC REST API to deploy the artifact. For jenkins deployments we made our own maven plugin which is called in its own job. On Tuesday, June 7, 2016 at 9:16:22 PM UTC-4, GBANE FETIGUE wrote: > > > Hi FOLKS , > >I have attached the referring document. I am trying to build a complete > Continuous Integration by Jenkins I have run all the process by following > the attach work flow until deploy the artifacts on artifactory but I kind > of looking for a MMC ( mule management Console) plugins to deploy the API > and the app on mule. I couldn't find any plugins up to date. I read about > Ion plugins but it's not working. any ideas is welcome > -- 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/2b132f63-64c4-45ed-8f2d-2bffbe68f627%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Script Security and Jenkinsfile
I am trying to write a Jenkinsfile for a project. The script security plugin is becoming a real pain. It seems the only way to add methods and operations is to run the job repeatedly failing each time and manually approve each failure. Needless to say this is a time-consuming process for all but the most trivial build scripts. Is there a better way to handle this? -- 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/e0b553f0-f039-4669-9e7b-306d15006b4c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Restartable Pipeline stages
Is there a way to implement a restartable stage that could be manually restarted? Often in Pipeline examples I see something like: - "Deploy" -> "Deploy Again" ->"Deploy Yet Again" It seems like this could be combined into a single step that could be reexecuted. Is this possible? -- 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/18a843ad-bdb2-4fc1-906c-683111eebb39%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Are jelly templates supported in email-ext with pipeline
Is support planed for a future release?
On Saturday, April 16, 2016 at 2:16:35 PM UTC-4, slide wrote:
>
> No, this is not currently supported. Token macro, which is the basis for
> the SCRIPT token doesn't currently support the type of object that pipeline
> uses.
>
> On Tue, Feb 9, 2016 at 10:32 AM Rinaldo DiGiorgio > wrote:
>
>> I am able to use email-ext with pipeline to send emails. I am trying to
>> use jelly templates. I do not see an option for the template processor in
>> the following. I tried adding *SCRIPT* to the body.
>>
>>
>> emailext attachLog: true, body: ' ${SCRIPT,
>> template="html/test.groovy"}', subject: 'Test of email', to: '
>> somea...@somedomain.com '
>>
>>
>>
>>
>>
>>
>> --
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/f7ed76fc-7c0d-4b5d-b582-5e39d468809d%40googlegroups.com
>>
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
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/f25baa0e-8051-4e1a-8f75-d3ed4fdea15f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Releasing Gitflow Projects with Jenkins
I know this has been brought up at least once before several years ago, but with time and the advent of Pipeline, I am wondering if best practices have changed. I am looking at automating releasing of Gitflow projects. Most of our projects have been stored in Subversion and we use the Maven Release Plugin which takes trunk, and tags it for release. Gitflow releasing is significantly more involved with a release branch being created and multiple (potentially error-prone) merges required. It seems like many of those deeply involved with Gitflow do not do CI/CD. Is there any advice or best practices for providing automated release processes for Git Flow? 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/171e6801-0d1b-4013-be2f-94e311907938%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Best Practices with LTS Updates
I am managing the Jenkins Server for my company. Recently, we moved from 1.609.3 to 1.625.3. I noticed however that the Required Core Dependencies for Pipe line skipped 1.625.x and went from 1.609.1 to 1.642.1. What are the best practices for selecting LTS versions to update? Would an upgrade from say 1.609.3 to 1.642.2 be safe? 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/56f97756-5dc8-453a-9b06-143a2ed4a088%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Is there any way for an Administrator to view a job as Non-Admin
Is there any way for an Administrator to view a job as Non-Admin? This would be helpful when testing roles and permissions. 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/5c17a63f-49ca-4d38-a07f-07613a9b2021%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Quiet Period and Build Now
Is there a way to assign a quiet period in Jenkins such that it only affects automatic builds and build triggers, but "Build Now" requests still happen without delay? -- 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/6e02001b-e9cc-434b-8c81-615f6f980709%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Workflows and SCM Polling
I am considering Workflows to automate build and release. Can a workflow be called in a CI polling manner? There is a "Poll SCM" build trigger but nowhere to input SCM details. What I would like to do is the following: 1) On SCM change execute a CI build. 2) Between stages prompt for whether build should be released 3) If the build is accepted, run the release stage, if not allow the build to age out. Is this a valid use case for workflows? -- 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/fd8f20f8-c26e-4d38-baa1-12cf38efa615%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Forking a process in Workflow
In case anyone sees this, I will post my workaround. 1) use writeFile to write the command-line to a file 2) create a script that reads the file, and does a fork-exec using the file contents as a command-line. On Monday, November 30, 2015 at 8:34:48 PM UTC-5, Mark Bidewell wrote: > > I am using Workflow to automate the Maven Release Plugin. Since Maven is > not directly supported via workflow, I use the sh step to call Maven. One > of the parameters this plugin takes is the password to use for checkins, > however if passwords contain special characters, the "sh" step will fail > due to shell interpretations. I was thinking I could get around this by > doing an execute() in workflow but that will only execute on the master. > In workflow, how can I execute a process on a slave without going though a > shell? > > 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/37ba6d5f-243c-4bec-97ce-d19d06614b31%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Forking a process in Workflow
I am using Workflow to automate the Maven Release Plugin. Since Maven is not directly supported via workflow, I use the sh step to call Maven. One of the parameters this plugin takes is the password to use for checkins, however if passwords contain special characters, the "sh" step will fail due to shell interpretations. I was thinking I could get around this by doing an execute() in workflow but that will only execute on the master. In workflow, how can I execute a process on a slave without going though a shell? 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/ee90b58c-2212-4437-a7e8-8ae1ab0a3d6c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Provide LTS 1.609.4 with security updates from 1.625.2 ?
We are in a similar position and another option (while exploring migration away from the Maven type) is that, while Maven itself must run JDK 7+, it can fork to a lower JDK. This forking is handled by Jenkins automatically and coiuld serve as a stopgap. On Tuesday, November 24, 2015 at 4:06:32 AM UTC-5, guido.wojke wrote: > > Hello everybody, > > due to a JDK 6 dependency on our build system we can't upgrade to Jenkins > 1.625.2 which forces a JDK 7 or higher to build maven job type. > We use the LTS 1.609.3 with the security workaround desribed here: > > https://jenkins-ci.org/content/mitigating-unauthenticated-remote-code-execution-0-day-jenkins-cli > > Is it possible to provide a LTS Version 1.609.4 with the security > update(s) provided in > the 1.625.1->1.625.2 update (f.e. the Important security fixes)? > > Best regards, > Guido > > -- 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/6fd2c69f-76a9-4019-a2c9-883579a9e375%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Workflow and executor use
When running my workflows, an executor stays allocated for the duration of the workflow. As I consider the possibility of complex flows that include pauses for things like QA approval, it seems likely that I will run out of executors. Are there ways in workflow to release the executor while paused between stages? 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/68897b34-e63b-48be-893c-707562e026af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins pre-build check of pom.xml
We do something similar to validate the connections section of a pom. We use an ant script to do the validation. On Tuesday, November 17, 2015 at 12:22:20 PM UTC-5, Andreas G. wrote: > > Hi guys, > > completely new to Jenkins and need help with a super simple thing. > > In my setup I would like to check if the "version" tag in the main pom.xml > of our project has the correct value. And if it has not the correct value > the build is supposed to fail. I looked around but my understanding of the > "pre-build step" (which seems the correct place for this kind of stuff) is > that should the script fail the build still carries on. > > Happy about any feedback. > > --Andreas > -- 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/cce35d18-7cd0-4f6d-884f-bb18ad2bd8a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Future of the Maven Project Type
Thanks that was my plan and use workflow to emulate as much of the release plugin functionality as possible (version verification for example). I just wanted to be sure that was the best course of action and there wasn't a better way forward. On Tuesday, November 17, 2015 at 10:38:08 AM UTC-5, Arnaud Héritier wrote: > > yes this one won't be compatible with workflow or freestyle jobs. > You'll have to replace it with a call of "release:prepare release;perform" > with few parameters defined as workflow user inputs or freestyle parameters. > > On Tue, Nov 17, 2015 at 3:29 PM, Mark Bidewell > wrote: > >> The primary usage is for the M2 release plugin integration. We are not >> making use of many other features. >> >> On Tuesday, November 17, 2015 at 10:25:00 AM UTC-5, Arnaud Héritier wrote: >>> >>> It mainly depends of the usage you have of it. >>> There are some specific features (post build deployment, snapshots >>> dependencies) which aren't available in others jobs types. >>> The migration to freestyle jobs is probably the easiest one from now as >>> you may have a large part of maven job types features but you'll need some >>> manual configuration. >>> Using the workflow is a solution but for now it doesn't cover all >>> integrations with plugins (contributions are welcome) and thus it may be >>> blocker depending of the current usage you have of it >>> Arnaud >>> >>> On Tue, Nov 17, 2015 at 1:43 PM, Mark Bidewell >>> wrote: >>> >>>> In my current position, I inherited a Jenkins server that makes heavy >>>> use of the Maven Project Type and M2 Release Plugin. As Jenkins is moving >>>> forward, I am now understanding why many people do not like that project >>>> type due to the shims needed to support Java 6 builds. >>>> >>>> What is the future of the Maven project type? should I be making plans >>>> to migrate from it? If so what is the best alternative (right now I am >>>> thinking workflows)? >>>> >>>> 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-use...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-users/45849d7b-990e-4232-a8dd-c4d37b9b2310%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-users/45849d7b-990e-4232-a8dd-c4d37b9b2310%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> - >>> Arnaud Héritier >>> http://aheritier.net >>> Mail/GTalk: aheritier AT gmail DOT com >>> Twitter/Skype : aheritier >>> >> -- >> 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-use...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/b613e575-7b8a-419b-b5a6-0aeb798e519d%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/b613e575-7b8a-419b-b5a6-0aeb798e519d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > - > Arnaud Héritier > http://aheritier.net > Mail/GTalk: aheritier AT gmail DOT com > Twitter/Skype : aheritier > -- 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/3a3718a8-f2f3-473c-a2eb-cdff95dcee25%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Future of the Maven Project Type
The primary usage is for the M2 release plugin integration. We are not making use of many other features. On Tuesday, November 17, 2015 at 10:25:00 AM UTC-5, Arnaud Héritier wrote: > > It mainly depends of the usage you have of it. > There are some specific features (post build deployment, snapshots > dependencies) which aren't available in others jobs types. > The migration to freestyle jobs is probably the easiest one from now as > you may have a large part of maven job types features but you'll need some > manual configuration. > Using the workflow is a solution but for now it doesn't cover all > integrations with plugins (contributions are welcome) and thus it may be > blocker depending of the current usage you have of it > Arnaud > > On Tue, Nov 17, 2015 at 1:43 PM, Mark Bidewell > wrote: > >> In my current position, I inherited a Jenkins server that makes heavy use >> of the Maven Project Type and M2 Release Plugin. As Jenkins is moving >> forward, I am now understanding why many people do not like that project >> type due to the shims needed to support Java 6 builds. >> >> What is the future of the Maven project type? should I be making plans to >> migrate from it? If so what is the best alternative (right now I am >> thinking workflows)? >> >> 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-use...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/45849d7b-990e-4232-a8dd-c4d37b9b2310%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/45849d7b-990e-4232-a8dd-c4d37b9b2310%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > - > Arnaud Héritier > http://aheritier.net > Mail/GTalk: aheritier AT gmail DOT com > Twitter/Skype : aheritier > -- 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/b613e575-7b8a-419b-b5a6-0aeb798e519d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Future of the Maven Project Type
In my current position, I inherited a Jenkins server that makes heavy use of the Maven Project Type and M2 Release Plugin. As Jenkins is moving forward, I am now understanding why many people do not like that project type due to the shims needed to support Java 6 builds. What is the future of the Maven project type? should I be making plans to migrate from it? If so what is the best alternative (right now I am thinking workflows)? 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/45849d7b-990e-4232-a8dd-c4d37b9b2310%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Using Jenkins to Vet New Build Environment
I am thinking about how to begin moving some projects on old JDKs to supported JDKs. I was wondering if there was a to run a build with normal settings, but then run a report-only (no artifact retention) build with a newer build environment to capture any compile or behavioral changes. Artifacts would still be generated by the older environment. Is there a way to do this without resorting to making all jobs matrix jobs? 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/310d7543-e100-4392-950a-fc4fd6108133%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
