[JIRA] (JENKINS-37867) Adding “Perform Maven Release” option from Jenkinsfile
Title: Message Title Harsha B commented on JENKINS-37867 Re: Adding “Perform Maven Release” option from Jenkinsfile Just revisiting this topic to see if there is any new development.Is there any plan to support maven project type as a template for pipeline projects? I am currently calling a DSL script from Jenkinsfile to create maven projects for master branch to get around this limitation. Works fine. But woulds like to know if pipelines would provide an option to the users to choose any project template they want in near future? 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-40130) Unable to create Jobs using job DSL in pipeline
Title: Message Title Harsha B commented on JENKINS-40130 Re: Unable to create Jobs using job DSL in pipeline Hi Arnaud/Daniel, Sorry I have been busy with some other things and could not respond earlier. Thanks for fixing this issue. We have upgraded the job DSL plugin and been using it for more than a month now. We haven't seen this issue so far. So I would think this is resolved afaik. Regards, Harsha 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-40130) Unable to create Jobs using job DSL in pipeline
Title: Message Title Harsha B updated an issue Jenkins / JENKINS-40130 Unable to create Jobs using job DSL in pipeline Change By: Harsha B Environment: CloudBees Jenkins Enterprise 2.7Job DSl v 1.51 Pipeline v 2.4Github Organization Folder v 1.4 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-40130) Unable to create Jobs using job DSL in pipeline
Title: Message Title Harsha B created an issue Jenkins / JENKINS-40130 Unable to create Jobs using job DSL in pipeline Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: jenkins_jobdsl_err.txt Components: github-organization-folder-plugin, job-dsl-plugin, pipeline Created: 2016/Nov/30 6:33 PM Environment: CloudBees Jenkins Enterprise 2.7 Job DSl v 1.51 Priority: Blocker Reporter: Harsha B I am running a pipeline job using Git Hub Organization folder plugin that scans a github organization and creates/runs jobs for all the repos that have Jenkinsfile in it. I have defined common pipeline scripts in a central git repo which is loaded by the Jenkinsfile and run. In my common pipeline script I am also creating/updating a Maven job for every master branch in the repo. I am doing this using Process Job DSL step from pipeline API. I am calling a groovy script that does this. It works fine for some time and at some point I am no longer able to create or update the new Maven jobs in my pipeline. There are no errors reported in build logs but the jobs do not get created. After this happens Job DSL sort of completely stops working for me. I cannot even create a simple test job using DSL. In the Jenkins system logs I see the below error messages. Can you please investigate this? This is blocking me from going live to production with my pipeline scripts.
[JIRA] (JENKINS-37867) Adding “Perform Maven Release” option from Jenkinsfile
Title: Message Title Harsha B commented on JENKINS-37867 Re: Adding “Perform Maven Release” option from Jenkinsfile Hi Jesse, Thanks for the response. Ok. That was my plan B. I would like to provide an option to the user in the pipeline job to trigger this maven release job. I am thinking of using jobDSL command to create a Maven release job from Jenkinsfile for every pipeline job that gets created. Is there a way to ensure that this step in Jenkinsfile is run only once (.i.e. the very first time a new pipeline job is created) ? I was thinking may I will set some env variable and run this step based on whether it is set or not. Is there a any other way of doing that? 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-37867) Adding “Perform Maven Release” option from Jenkinsfile
Title: Message Title Harsha B created an issue Jenkins / JENKINS-37867 Adding “Perform Maven Release” option from Jenkinsfile Issue Type: Bug Assignee: Jesse Glick Components: pipeline-build-step-plugin Created: 2016/Aug/31 7:50 PM Priority: Critical Reporter: Harsha B 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. Add Comment
[JIRA] (JENKINS-34563) Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine
Title: Message Title Harsha B commented on JENKINS-34563 Re: Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine Hi Allan, I tried this fix. It did not work for me. The behaviour is same as before. This is what I have tried: I downloaded the JENKINS-32155 branch and built it by running mvn clean install from the root. I then manually installed the "github-branch-source.hpi" in to Jenkins and restarted the jenkins. I have attached the screenshot of my plugin manager page for reference. What am I missing here? Can you please help? 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-34563) Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine
Title: Message Title Harsha B updated an issue Jenkins / JENKINS-34563 Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine Change By: Harsha B Attachment: Screen Shot 2016-08-23 at 11.03.10 AM.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-34563) Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine
Title: Message Title Harsha B commented on JENKINS-34563 Re: Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine I am facing the exact same issue being reported here. I am using Jenkins v 1.651.3 ; Github organization folder plugin v 1.4 & Pipeline plugin v 2.2 I am using Enterprise Github. My Github organization job does not detect new repository creation automatically. It only detects them if they are forked from other organizations and they already contain a Jenkinsfile. 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.
