[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title
kyle ian commented on JENKINS-57899
Re: Jira site configuration lost after a reboot
Working off Justin Holzer's workaround, the below worked for me in script console – I also tried this as a file in $JENKINS_HOME/ref/init.groovy.d to get loaded on boot, and it appeared to blow away the site record entirely, so I don't recommend trying that. Opted for new JiraSite to overwrite existing due to lack of setUrl method.
import hudson.plugins.jira.*
jiraSites = JiraGlobalConfiguration.get().getSites()
jiraSites[0] = new JiraSite("https://my-jira-site.atlassian.net/")
jiraSites[0].setCredentialsId("some-credential-id")
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.1390.1562179020329%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58243) P4-plugin Multiple jobs with same stream do not trigger
Title: Message Title
kyle ian created an issue
Jenkins / JENKINS-58243
P4-plugin Multiple jobs with same stream do not trigger
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-06-27 21:06
Environment:
Jenkins 2.181 P4 Plugin 1.10.0 Windows 10 Pro
Labels:
perforce p4-plugin p4
Priority:
Minor
Reporter:
kyle ian
I have Perforce and Swarm set up to trigger the Jenkins p4 plugin as written in the docs, which I have confirmed works for me on a git multibranch pipeline, where the branches' Jenkinsfile specifies `pipelineTriggers([p4Trigger()])` as part of its properties and the branch specified matches a stream name. In an effort to do away with the multibranch pipeline for ease of adding new streams, I'm moving toward a job DSL bootstrap where I build out a set of folders under which many job pipelines are created for each stream. One of these subjobs, which shares the name of the stream ( "build-refactor" ) will act as the job to be triggered by p4trigger, and then trigger other pipeline jobs in the folder; this p4trigger job I have set up this up as follows in the pipelineJob config:
pipelineJob("${streamFolder}/${stream.key}") {
configure { project ->
project / 'triggers' << 'org.jenkinsci.plugins.p4.trigger.P4Trigger'{
spec ''
}
}
[JIRA] (JENKINS-58243) P4-plugin Multiple jobs with same stream name do not trigger
Title: Message Title kyle ian updated an issue Jenkins / JENKINS-58243 P4-plugin Multiple jobs with same stream name do not trigger Change By: kyle ian Summary: P4-plugin Multiple jobs with same stream name do not trigger Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200306.1561669582000.11038.1561669620183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55214) NullPointerException when starting a pipeline in a multibranch project
Title: Message Title
kyle ian edited a comment on JENKINS-55214
Re: NullPointerException when starting a pipeline in a multibranch project
[~p4karl]Steps I took while investigating: 1. Updated `description` to have comma after value - all sibiling pipelines still failed with NPE 2. Removed `ParameterDefinitionProperty` from pipeline props entirely - offending pipeline ran successfully without prop with no NPE, sibiling pipelines failed with NPE still 3. Added parameterDefinitionProperty back, removing redundant `name` 4. Rescanned multibranch pipeline after (3) 5. All sibiling multibranch pipelines run successfully without NPEExample: {code:java}properties([ pipelineTriggers([p4Trigger()]), [$class: 'ParametersDefinitionProperty',parameterDefinitions:[ [$class: 'hudson.model.BooleanParameterDefinition', name: 'I_AM_A_BOOL_PARAMETER_NAME', name: 'I_AM_AN_UNNECESSARY_REDUNDANT_BOOL_PARAMETER_NAME', description: 'I am a description that is missing a comma after my string ends, which will be detected by linting on a given branch's branchs pipeline, but other pipelines belonging to the same parent multibranch pipeline will fail with JENKINS-55214 NPE until this is corrected.' defaultValue: false]] ]]){code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196286.1544938736000.400.1557843360383%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55214) NullPointerException when starting a pipeline in a multibranch project
Title: Message Title kyle ian commented on JENKINS-55214 Re: NullPointerException when starting a pipeline in a multibranch project Karl Wirth Steps I took while investigating: 1. Updated `description` to have comma after value - all sibiling pipelines still failed with NPE 2. Removed `ParameterDefinitionProperty` from pipeline props entirely - offending pipeline ran successfully without prop with no NPE, sibiling pipelines failed with NPE still 3. Added parameterDefinitionProperty back, removing redundant `name` 4. Rescanned multibranch pipeline after (3) 5. All sibiling multibranch pipelines run successfully without NPE Example: properties([ pipelineTriggers([p4Trigger()]), [$class: 'ParametersDefinitionProperty', parameterDefinitions: [ [$class: 'hudson.model.BooleanParameterDefinition', name: 'I_AM_A_BOOL_PARAMETER_NAME', name: 'I_AM_AN_UNNECESSARY_REDUNDANT_BOOL_PARAMETER_NAME', description: 'I am a description that is missing a comma after my string ends, which will be detected by linting on a given branch's pipeline, but other pipelines belonging to the same parent multibranch pipeline will fail with JENKINS-55214 NPE until this is corrected.' defaultValue: false] ] ] ]) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196286.1544938736000.396.1557843360303%40Atlassian.JIRA. F
[JIRA] (JENKINS-55214) NullPointerException when starting a pipeline in a multibranch project
Title: Message Title kyle ian commented on JENKINS-55214 Re: NullPointerException when starting a pipeline in a multibranch project Ran into this today on 1.9.7 - it appeared to me the cause was a poorly formed parameter block passed to the (node) pipeline on one of my branches. Added new description to parameter on one branch, missing comma after description (groovy linter would've picked it up) All builds under multi pipeline failed with error noted in OP when solely one of the multipipeline branches had bad parameter configuration fixed comma on bad branch parameter configuration (single branch), rescanned multipipeline reran pipeline build for each branch, confirmed fixing that parameter block to be well formed resulted in all successful pipeline builds for each branch I have not been able to reproduce it after fixing this parameter block // have not tried breaking it again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196286.1544938736000.1794.1557776520156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41241) Jenkins Failes to startup, Without updatating any plugin (WebAppMain.java:248)
Title: Message Title kyle ian commented on JENKINS-41241 Re: Jenkins Failes to startup, Without updatating any plugin (WebAppMain.java:248) The above suggestion to remove the cloudbees plugin from the plugins folder results in Jenkins losing reference of the prior existing jobs / workspaces. Is there a better way to solve this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
