[JIRA] (JENKINS-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title Jae Gangemi started work on JENKINS-52669 Change By: Jae Gangemi Status: Open In Progress 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.192545.1532070393000.21918.1559742481431%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title Jae Gangemi resolved as Fixed Jenkins / JENKINS-52669 IndexOutOfBoundsException after upgrade to 1.2.3 Change By: Jae Gangemi Status: In Progress Resolved Resolution: Fixed 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.192545.1532070393000.21930.1559742481629%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title Jae Gangemi commented on JENKINS-52669 Re: IndexOutOfBoundsException after upgrade to 1.2.3 fixed in 1.2.6 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.192545.1532070393000.21910.1559742481198%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title Jae Gangemi assigned an issue to Jae Gangemi Jenkins / JENKINS-52669 IndexOutOfBoundsException after upgrade to 1.2.3 Change By: Jae Gangemi Assignee: Jae Gangemi 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.192545.1532070393000.21932.1559742481655%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52144) unable to provision pods w/ plugin > 1.4.1
Title: Message Title Jae Gangemi commented on JENKINS-52144 Re: unable to provision pods w/ plugin > 1.4.1 any chance of seeing movement on this? JENKINS-50659 references the same issue i am where the behavior changed from 1.4 to 1.5 and it seems to all be related to the working directory between versions. i tried the latest version 1.12.2 and it's still broken. 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.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title Jae Gangemi commented on JENKINS-15570 Re: Coverage report includes classes that have been excluded from Jacoco analysis i'm confused as to why this information just isn't part of the generated results file in the first place as a block that indicates what to exclude. perhaps even better would just be excluding the classes from the result file outright. disclaimer: i have not looked into how the maven plugin works when i choose to generate a report, but it does do the proper exclusions. if the plugin needs to parse the pom to figure this out, then that is the fix but that doesn't really seem like the correct solution here b/c what if i'm a nodejs project that is able to generate coverage reports in jacoco format? there's not going to be any pom to parse for exclusions in that case. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-16705) Native support for settings-security.xml (i. e. encrypted passwords)
Title: Message Title
Jae Gangemi commented on JENKINS-16705
Re: Native support for settings-security.xml (i. e. encrypted passwords)
is there any movement on this issue? i would like to see the ability for the plugin to just drop a security-settings.xml file in place w/ the encrypted master password supplied from the credentials plugin. the plugin could drop the file directly in the .m2 directory or the location can be passed to maven using {{-Dsettings.security}} as described here: https://stackoverflow.com/questions/23782409/specify-custom-location-of-maven-security-settings-xml-file
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-16705) Native support for settings-security.xml (i. e. encrypted passwords)
Title: Message Title
Jae Gangemi edited a comment on JENKINS-16705
Re: Native support for settings-security.xml (i. e. encrypted passwords)
is there any movement on this issue? i would like to see the ability for the plugin to just drop a {{security-settings.xml}} file in place w/ the encrypted master password supplied from the credentials plugin.the plugin could drop the file directly in the {{.m2}} directory or the location can be passed to maven using \ { \ { {{ -Dsettings.security}} }} as described here: [ https://stackoverflow.com/questions/23782409/specify-custom-location-of-maven-security-settings-xml-file ]
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-50293) Repository Connector Plugin does not use Jenkins configured proxy correctly
Title: Message Title Jae Gangemi resolved as Fixed releases as 1.2.4, should be available shortly Jenkins / JENKINS-50293 Repository Connector Plugin does not use Jenkins configured proxy correctly Change By: Jae Gangemi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-50293) Repository Connector Plugin does not use Jenkins configured proxy correctly
Title: Message Title Jae Gangemi updated JENKINS-50293 Jenkins / JENKINS-50293 Repository Connector Plugin does not use Jenkins configured proxy correctly Change By: Jae Gangemi Status: Resolved In Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50293) Repository Connector Plugin does not use Jenkins configured proxy correctly
Title: Message Title Jae Gangemi updated JENKINS-50293 Jenkins / JENKINS-50293 Repository Connector Plugin does not use Jenkins configured proxy correctly Change By: Jae Gangemi Status: In Review Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50293) Repository Connector Plugin does not use Jenkins configured proxy correctly
Title: Message Title Jae Gangemi assigned an issue to Jae Gangemi Jenkins / JENKINS-50293 Repository Connector Plugin does not use Jenkins configured proxy correctly Change By: Jae Gangemi Assignee: Jae Gangemi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50963) UpdatePolicy reset to default on edit
Title: Message Title Jae Gangemi closed an issue as Fixed Jenkins / JENKINS-50963 UpdatePolicy reset to default on edit Change By: Jae Gangemi Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50963) UpdatePolicy reset to default on edit
Title: Message Title Jae Gangemi resolved as Fixed releases as 1.2.4, should be available shortly Jenkins / JENKINS-50963 UpdatePolicy reset to default on edit Change By: Jae Gangemi Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Jae Gangemi commented on JENKINS-50525 Re: Error When Provisioning Slave: mountPath: Required value i'm currently running 1.4.1 w/o any issue. if you don't have the option to roll back to that, you can download it directly from the jenkins maven repository and install it, which is what i did. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Jae Gangemi commented on JENKINS-50525 Re: Error When Provisioning Slave: mountPath: Required value i have no other values set in the pod template other then the container definition. i am currently using version 0.11 - i had tried newer 1.x versions but had to roll back b/c of that issue where an additional container was spun up which i believe was fixed in 1.3.1. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Jae Gangemi commented on JENKINS-50525 Re: Error When Provisioning Slave: mountPath: Required value Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Jae Gangemi updated an issue Jenkins / JENKINS-50525 Error When Provisioning Slave: mountPath: Required value Change By: Jae Gangemi Attachment: image-2018-04-10-10-48-36-384.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Jae Gangemi commented on JENKINS-50525 Re: Error When Provisioning Slave: mountPath: Required value i tried mounting in a host volume just to see if that populate the field but i still got the same error. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Jae Gangemi commented on JENKINS-50525 Re: Error When Provisioning Slave: mountPath: Required value both Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title
Jae Gangemi commented on JENKINS-50525
Re: Error When Provisioning Slave: mountPath: Required value
i'm now getting this error after upgrading for a pod template that was working before and has no volumes/mount paths associated with it at all
Error in provisioning; agent=KubernetesSlave name: kubectl-8-debian-lv201, template=PodTemplate{inheritFrom='', name='kubectl-8-debian', namespace='', label='kubectl-8-debian', nodeSelector='', nodeUsageMode=NORMAL, workspaceVolume=org.csanchez.jenkins.plugins.kubernetes.volumes.workspace.EmptyDirWorkspaceVolume@2d52e6f4, containers=[ContainerTemplate{name='jnlp', image='registry.battery-park.conductor.com/jenkins-slave-8-kubectl-debian', alwaysPullImage=true, workingDir='', command='', args='${computer.jnlpmac} ${computer.name}', ttyEnabled=true, resourceRequestCpu='', resourceRequestMemory='', resourceLimitCpu='', resourceLimitMemory='', livenessProbe=org.csanchez.jenkins.plugins.kubernetes.ContainerLivenessProbe@774c827b}]}
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: http://jenkins-kubernetes-master.infra.us-east-1.conductor.sh/api/v1/namespaces/beta/pods. Message: Pod "kubectl-8-debian-lv201" is invalid: spec.containers[0].volumeMounts[0].mountPath: Required value. Received status: Status(apiVersion=v1, code=422, details=StatusDetails(causes=[StatusCause(field=spec.containers[0].volumeMounts[0].mountPath, message=Required value, reason=FieldValueRequired, additionalProperties={})], group=null, kind=Pod, name=kubectl-8-debian-lv201, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=Pod "kubectl-8-debian-lv201" is invalid: spec.containers[0].volumeMounts[0].mountPath: Required value, metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=Invalid, status=Failure, additionalProperties={}).
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:472)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:411)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:381)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:344)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleCreate(OperationSupport.java:227)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:756)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.create(BaseOperation.java:334)
at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:105)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:288)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title Jae Gangemi commented on JENKINS-15570 Re: Coverage report includes classes that have been excluded from Jacoco analysis is there any futher movement on this issue? configuring exclusions in maven and jenkins is not a viable work around. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-47641) FAILURE during Repository Connector build step
Title: Message Title Jae Gangemi commented on JENKINS-47641 Re: FAILURE during Repository Connector build step are you able to reproduce this w/ a jar that is located on maven central? does this occur for only SNAPSHOT jars or also released jars? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41766) expose environment variable to indicate release
Title: Message Title Jae Gangemi commented on JENKINS-41766 Re: expose environment variable to indicate release i use the env var to explicitly enable a maven profile that does some extra things, so i need it to be set in the build environment. i believe this should just require an implementation of EnvironmentContributingAction and the corresponding jelly bits that go along with it. i would love to just contribute this back as a PR myself but i'm not sure i can find the time right now. of course, if you tell me it will be 2 months before you can get to this b/c you have other things on your plate, i'll try and find the time. 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-41766) expose environment variable to indicate release
Title: Message Title Jae Gangemi commented on JENKINS-41766 Re: expose environment variable to indicate release i have only ever had the need to export a single env var to indicate a release build but that doesn't mean others may not. i unfortunately can't switch over to using the plugin full time w/o this, so i'm all for whatever gets me the ability to at least specify one env var the fastest. 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-41766) expose environment variable to indicate release
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-41766 expose environment variable to indicate release Issue Type: Bug Assignee: Stanley Hillner Components: unleash-plugin Created: 2017/Feb/06 6:01 PM Priority: Minor Reporter: Jae Gangemi it would be great if the plugin could expose an environment variable, similar to the m2-plugin, to indicate a release is being performed. using IS_M2RELEASEBUILD as would be a good choice as it is default used by the m2-plugin and would allow users to switch between the two in jenkins w/o the need to make pom and/or configuration changes. Add Comment
[JIRA] (JENKINS-41040) ssh fails to run after upgrade to 0.10
Title: Message Title Jae Gangemi resolved as Duplicate Jenkins / JENKINS-41040 ssh fails to run after upgrade to 0.10 Change By: Jae Gangemi Status: Open Resolved Resolution: Duplicate 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-41040) ssh fails to run after upgrade to 0.10
Title: Message Title Jae Gangemi commented on JENKINS-41040 Re: ssh fails to run after upgrade to 0.10 i mis-understood the work around in the other bug. my issue has been resolved and this a dup. 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-40847) JNLP slave pod gets created even when a different slave is configured
Title: Message Title Jae Gangemi commented on JENKINS-40847 Re: JNLP slave pod gets created even when a different slave is configured JENKINS-41040 is related 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-41040) ssh fails to run after upgrade to 0.10
Title: Message Title Jae Gangemi commented on JENKINS-41040 Re: ssh fails to run after upgrade to 0.10 no - i am running custom containers and the suggested work around will not work for this same reason: https://issues.jenkins-ci.org/browse/JENKINS-40847?focusedCommentId=282761=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-282761 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-41040) ssh fails to run after upgrade to 0.10
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-41040 ssh fails to run after upgrade to 0.10 Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2017/Jan/12 4:52 PM Priority: Minor Reporter: Jae Gangemi after upgrading from 0.9 to 0.10, my slaves no longer work and the following exception is thrown: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress g...@github.com:condevops/hello-world-jenkins.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: error: cannot run ssh: No such file or directory fatal: unable to fork at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1772) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1516) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:67) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:318) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:515) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:332) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 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)
[JIRA] (JENKINS-39014) expose underlying host ip as environment variable
Title: Message Title Jae Gangemi commented on JENKINS-39014 Re: expose underlying host ip as environment variable i'm already doing something similar. for maven based builds, the docker-maven-plugin exposes the internal ip address of the container, so it's easy to connect in that manner. for other builds i was just going to use a combination of docker commands to inspect the container and figure out it's internal ip. having the host ip exposed as an env variable would just simplify this a bit b/c then we could just connect to that ip and whatever random port the service was exposed on. 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-39077) unable to provision pods using 0.9 snapshot
Title: Message Title Jae Gangemi commented on JENKINS-39077 Re: unable to provision pods using 0.9 snapshot my co-worker and i tracked this down by comparing the specs generated from 0.8 to 0.9 and found this difference: works: volumeMounts: - mountPath: /var/run/docker.sock name: volume-0 workingDir: /home/jenkins not working: volumeMounts: - mountPath: /var/run/docker.sock name: volume-0 - mountPath: /home/jenkins name: workspace-volume workingDir: /home/jenkins so it seems that extra mountPath 'overwrites' /home/jenkins when the container starts. if i unset the Working directory field in the template configuration, i can successfully run my images. i am not sure if the value of Working directory is set by default or if it got carried over from the Jenkins slave root directory field in 0.8. 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
[JIRA] (JENKINS-39085) namespaces don't seem to be created
Title: Message Title Jae Gangemi commented on JENKINS-39085 Re: namespaces don't seem to be created could that be documented somewhere? 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-39085) namespaces don't seem to be created
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-39085 namespaces don't seem to be created Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Oct/18 10:16 PM Priority: Minor Reporter: Jae Gangemi the plugin does not create the namespace i specify in the configuration. when i go to the kubes dashboard, it does not appear in the dropdown and it does not appear when i run the associated kubectl command. the documentation doesn't say anything about this, so i'm not sure if this is an actual bug or if it's my responsibility to create the namespaces in the cluster upfront. Add Comment
[JIRA] (JENKINS-39077) unable to provision pods using 0.9 snapshot
Title: Message Title Jae Gangemi commented on JENKINS-39077 Re: unable to provision pods using 0.9 snapshot also - the scripts directory is in /home/jenkins and the Dockerfile sets that as the WORKDIR right before it sets that script as the entry point 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-39077) unable to provision pods using 0.9 snapshot
Title: Message Title
Jae Gangemi commented on JENKINS-39077
Re: unable to provision pods using 0.9 snapshot
Events:
FirstSeenLastSeenCountFromSubobjectPathTypeReasonMessage
--------
6m6m1{default-scheduler }NormalScheduledSuccessfully assigned java8-mvn-slave-28081e60dd37c to ip-172-22-1-147.ec2.internal
6m6m1{kubelet ip-172-22-1-147.ec2.internal}spec.containers{java8-mvn-slave}NormalPullingpulling image "registry.battery-park.conductor.com/jenkins-slave-maven-debian"
6m6m1{kubelet ip-172-22-1-147.ec2.internal}spec.containers{java8-mvn-slave}NormalPulledSuccessfully pulled image "registry.battery-park.conductor.com/jenkins-slave-maven-debian"
6m6m1{kubelet ip-172-22-1-147.ec2.internal}spec.containers{java8-mvn-slave}NormalCreatedCreated container with docker id 451bce1c3290; Security:[seccomp=unconfined]
6m6m1{kubelet ip-172-22-1-147.ec2.internal}spec.containers{java8-mvn-slave}WarningFailedFailed to start container with docker id 451bce1c3290 with error: Error response from daemon: Container command 'scripts/jenkins-slave.sh' not found or does not exist.
6m6m1{kubelet ip-172-22-1-147.ec2.internal}WarningFailedSyncError syncing pod, skipping: failed to "StartContainer" for "java8-mvn-slave" with RunContainerError: "runContainer: Error response from daemon: Container command 'scripts/jenkins-slave.sh' not found or does not exist."
i don't understand the Container command 'scripts/jenkins-slave.sh' not found or does not exist. error. this container runs fine in the 0.8 version of the plugin and nothing has changed there.
Add Comment
[JIRA] (JENKINS-39077) unable to provision pods using 0.9 snapshot
Title: Message Title Jae Gangemi commented on JENKINS-39077 Re: unable to provision pods using 0.9 snapshot the Unrecognized input header: 50 is all i have been able to get in terms of logs. i am going to try upgrading my version of docker to see if it yields any changes. i'll report back whatever extra logs come out of this. 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-39077) unable to provision pods using 0.9 snapshot
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-39077 unable to provision pods using 0.9 snapshot Issue Type: New Feature Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Oct/18 7:58 PM Priority: Minor Reporter: Jae Gangemi i'm compiling the project from source so i can try out the tty functionality and i am unable to provision any pods/slaves now. is what's on master not in a usable state? the jenkins logs don't give much information and the error i see in kubernetes is this: Unrecognized input header: 50 Add Comment
[JIRA] (JENKINS-39013) allow docker container to run with tty
Title: Message Title Jae Gangemi commented on JENKINS-39013 Re: allow docker container to run with tty where?!!?? i do not see one. 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-39014) expose underlying host ip as environment variable
Title: Message Title Jae Gangemi commented on JENKINS-39014 Re: expose underlying host ip as environment variable now that i look at this a bit more, the pipeline doesn't necessarily fit my use case. the underlying build process is what starts/stops the necessary containers. they aren't meant to be scheduled by kubernetes as is the case here. having said that, i wouldn't mind having a programmatic way to create containers, so what would be the best way to expose some default container configurations that can be shared across multiple pods? 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-39014) expose underlying host ip as environment variable
Title: Message Title Jae Gangemi commented on JENKINS-39014 Re: expose underlying host ip as environment variable and what if i don't want to use pipelines? can this not be added as an option to enable the the GUI? 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-39014) expose underlying host ip as environment variable
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-39014 expose underlying host ip as environment variable Issue Type: New Feature Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Oct/16 3:02 PM Priority: Minor Reporter: Jae Gangemi would it be possible to expose the ip address of the underlying host node to the docker containers in an environment variable? i am running builds inside the container and those builds have integration tests that need to talk to a mysql container. i am able to spin up the container fine by mounting in /var/run/docker.sock but i'm unable to communicate w/ it b/c i don't know it's ip address and linking the containers is not an option. i do have some work arounds available, but this would be a huge help if it's possible. Add Comment
[JIRA] (JENKINS-39013) allow docker container to run with tty
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-39013 allow docker container to run with tty Issue Type: New Feature Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Oct/16 2:50 PM Priority: Minor Reporter: Jae Gangemi i would like to be able to do gpg signing of git commits inside of the docker build slaves however this does not seem to be possible w/o running the container w/ a sudo-tty. can this be added as an option when launching a slave? i am also open to other suggestions how how this could be made to work. Add Comment
[JIRA] (JENKINS-38944) webhook is not registering on creation
Title: Message Title Jae Gangemi commented on JENKINS-38944 Re: webhook is not registering on creation i don't see anywhere that provided access to the Job class unless it's in AbstractWorkflowBranchProjectFactory. i will try to dig around a bit more on this over the weekend. i'm really hoping one of the maintainers can respond and offer some direction, insight. 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-38975) Implement PR job rebuild on pull request comment
Title: Message Title Jae Gangemi commented on JENKINS-38975 Re: Implement PR job rebuild on pull request comment since you seem to have a bit more knowledge in this area then i do right now... how do you deal w/ setting up the webhook for a new project (see JENKINS-38944)? 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-38975) Implement PR job rebuild on pull request comment
Title: Message Title Jae Gangemi commented on JENKINS-38975 Re: Implement PR job rebuild on pull request comment +1 for this. is it not possible to configure the trigger string via the UI? what is the current value of the trigger? 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-38944) webhook is not registering on creation
Title: Message Title Jae Gangemi commented on JENKINS-38944 Re: webhook is not registering on creation i spent some time looking into this and i don't see any way in the current implementation this can be accomplished. is there some way to get a reference to the Job object(s) that are created once the scan completes? from there all that should be required (i think) is to get a reference to com.cloudbees.jenkins.GitHubWebHook and call registerHookFor passing it the Job object(s). 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-38944) webhook is not registering on creation
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-38944 webhook is not registering on creation Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2016/Oct/12 11:43 PM Priority: Minor Reporter: Jae Gangemi the plugin does not seem to be registering the webhook when i create a new project. i have the 'manage hooks' checkbox checked in the github plugin section and the webhook does register if i click 'register for all projects', but i need this to be automatically get up when the project gets created. Add Comment
[JIRA] (JENKINS-36536) Trend graph on pipeline project page
Title: Message Title Jae Gangemi commented on JENKINS-36536 Re: Trend graph on pipeline project page is there any movement on this? we are trying to move to using pipelines and this would be a great help, thanks!! 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-38715) Container instance cannot be empty error
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-38715 Container instance cannot be empty error Issue Type: Bug Assignee: Jan Roehrich Components: amazon-ecs-plugin Created: 2016/Oct/04 8:21 PM Priority: Minor Reporter: Jae Gangemi i am getting the following error when trying to launch a build into ecs: com.amazonaws.services.ecs.model.InvalidParameterException: Container instance cannot be empty. (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException; Request ID: 0c26d03e-8a6c-11e6-be2f-71463a1d5d9f) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1307) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:894) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:597) at com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:363) at com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttpClient.java:329) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:308) at com.amazonaws.services.ecs.AmazonECSClient.invoke(AmazonECSClient.java:) at com.amazonaws.services.ecs.AmazonECSClient.describeContainerInstances(AmazonECSClient.java:876) at com.cloudbees.jenkins.plugins.amazonecs.ECSService.waitForSufficientClusterResources(ECSService.java:180) at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:255) at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:237) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at
[JIRA] (JENKINS-36823) Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles
Title: Message Title Jae Gangemi commented on JENKINS-36823 Re: Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles is there any forward movement on this? 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-37970) allow exclusions to be configured for a template
Title: Message Title Jae Gangemi commented on JENKINS-37970 Re: allow exclusions to be configured for a template ok - i'm basically looking to use a combination of this plugin and the rest api to programmatically create jobs, so while not ideal, for now i can just manipulate the xml of the job template before i resubmit it to create a new job. 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-37971) EZ-Templates support Github plugin
Title: Message Title Jae Gangemi edited a comment on JENKINS-37971 Re: EZ-Templates support Github plugin sorry for my delayed response...the plugin exposes two fields, the url and a 'display' name which is then used to set branch statuses in github. we use a (poorly named) status called 'default' so it would be nice to leave the url field empty but define the status field so everything else inherits from it. i'm doing a mixed template where some things are controlled via the plugin and then i inject the rest when i create the job (i use the jenkins api to download the template, populate what i want and then create the job), so it's not a big deal to control the property that way.thanks for taking care of this. 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-37971) EZ-Templates support Github plugin
Title: Message Title Jae Gangemi commented on JENKINS-37971 Re: EZ-Templates support Github plugin sorry for my delayed response... the plugin exposes two fields, the url and a 'display' name which is then used to set branch statuses in github. we use a (poorly named) status called 'default' so it would be nice to leave the url field empty but define the status field so everything else inherits from it. 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-37971) support the github plugin for exclusions
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-37971 support the github plugin for exclusions Issue Type: New Feature Assignee: Joel Johnson Components: ez-templates-plugin Created: 2016/Sep/05 9:30 PM Priority: Minor Reporter: Jae Gangemi please add support for ignoring the github plugin "github@1.21.1"> url display even better would be to allow the projectUrl to be ignored but the displayName cloned (it can be used to set the name of the status set on a branch. Add Comment
[JIRA] (JENKINS-37970) allow exclusions to be configured for a template
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-37970 allow exclusions to be configured for a template Issue Type: New Feature Assignee: Joel Johnson Components: ez-templates-plugin Created: 2016/Sep/05 9:26 PM Priority: Minor Reporter: Jae Gangemi it would be great to be able to configure the exclusions a child template should use from the parent itself. for example, right now i have to manually exclude the scm section for every project i create. Add Comment This message
[JIRA] (JENKINS-37903) IllegalStateException thrown during release
Title: Message Title Jae Gangemi commented on JENKINS-37903 Re: IllegalStateException thrown during release ok - it looks like this is an issue w/ the way jenkins checks out projects w/ a detached HEAD. i am setting the "check out to a specific local branch" option, but that does not seem to have an effect. i'll file a bug in against the maven plugin for this as i can reproduce this locally using the same steps jenkins uses to check out the project. 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-37903) IllegalStateException thrown during release
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-37903 IllegalStateException thrown during release Issue Type: New Feature Assignee: Stanley Hillner Components: unleash-plugin Created: 2016/Sep/01 3:46 PM Priority: Minor Reporter: Jae Gangemi i'm getting the following exception using the 2.1.1 version of the maven plugin and the 1.2.1 of the jenkins plugin and i'm getting the following error: Caused by: java.lang.IllegalStateException: No from revision set (start revision of the reversion)! at com.google.common.base.Preconditions.checkState(Preconditions.java:174) at com.itemis.maven.plugins.unleash.scm.requests.RevertCommitsRequest$Builder.build(RevertCommitsRequest.java:187) at com.itemis.maven.plugins.unleash.steps.actions.SetNextDevVersion.rollback(SetNextDevVersion.java:129) ... 42 more i'm about to start looking into adding the 'release as a post build step' functionality i mentioned in JENKINS-37401 and will look at this as well, but in case you have any ideas right away...
[JIRA] (JENKINS-37401) trigger release via post build step
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-37401 trigger release via post build step Issue Type: New Feature Assignee: Stanley Hillner Components: unleash-plugin Created: 2016/Aug/14 3:41 PM Priority: Minor Reporter: Jae Gangemi i was wondering if you would consider adding (or accept as a PR) a post build step that would allow one to invoke this plugin when a snapshot build is successful which would allow for a more continuous delivery process. right now the only way to achieve this is to create a separate job that invokes the goals directly which means i need to maintain two build configurations, etc. Add Comment
[JIRA] (JENKINS-29519) Capability to trigger m2 release plugin from API or command line
Title: Message Title Jae Gangemi commented on JENKINS-29519 Re: Capability to trigger m2 release plugin from API or command line i would like to see this added in the form of a post build step so that i could have a single job that can be used for a full ci/cd process. 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] [configurationslicing-plugin] (JENKINS-35271) add support for the maven-release-plugin
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-35271 add support for the maven-release-plugin Issue Type: New Feature Assignee: mdonohue Components: configurationslicing-plugin Created: 2016/Jun/01 3:53 PM Priority: Minor Reporter: Jae Gangemi please add support for the maven-release-plugin, thanks!! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Jae Gangemi commented on JENKINS-33434 Re: no post build step to set status to 'success' please see the attached screenshots, i'm not listing them all out by hand. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Jae Gangemi updated an issue Jenkins / JENKINS-33434 no post build step to set status to 'success' Change By: Jae Gangemi Attachment: Screen Shot 2016-04-11 at 6.45.36 PM.png Attachment: Screen Shot 2016-04-11 at 6.45.55 PM.png Attachment: Screen Shot 2016-04-11 at 6.46.04 PM.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Jae Gangemi commented on JENKINS-33434 Re: no post build step to set status to 'success' any updates on this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Jae Gangemi commented on JENKINS-33434 Re: no post build step to set status to 'success' github api: 1.72.1 github plugin: 1.17.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Jae Gangemi commented on JENKINS-33434 Re: no post build step to set status to 'success' please see the two attached screen shots that show the drop downs for the pre-build step and post-build step. i only see any option to see the status to 'pending' for the post build step and no option to set it to 'success'. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Jae Gangemi updated an issue Jenkins / JENKINS-33434 no post build step to set status to 'success' pre-build step Change By: Jae Gangemi Attachment: Screen Shot 2016-03-11 at 10.21.35 AM.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Jae Gangemi updated an issue Jenkins / JENKINS-33434 no post build step to set status to 'success' post-build step Change By: Jae Gangemi Attachment: Screen Shot 2016-03-11 at 10.21.47 AM.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Jae Gangemi commented on JENKINS-33434 Re: no post build step to set status to 'success' i don't really understand how setting the 'success' status at the end of the build doesn't fall into the regular 90% of use cases, as opposed to some custom statuses that are specific to someone's organization, but whatever. i appreciate the response. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Jae Gangemi commented on JENKINS-33434 Re: no post build step to set status to 'success' would you mind explaining why the github plugin works this way instead of just directing me to another plugin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-33434 no post build step to set status to 'success' Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 09/Mar/16 7:01 PM Priority: Minor Reporter: Jae Gangemi there is only a post build step to set the status to 'pending', which doesn't make a lot of sense and i don't want to use a post build action to set this. Add Comment This message was sent by
[JIRA] [linenumbers-plugin] (JENKINS-33105) preserve blank/empty lines
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-33105 preserve blank/empty lines Issue Type: Bug Assignee: Vincent Latombe Attachments: Screen Shot 2016-02-23 at 9.02.19 AM.png Components: linenumbers-plugin Created: 23/Feb/16 2:03 PM Priority: Minor Reporter: Jae Gangemi the plugin collapses empty lines (pls see screenshot) and it would be great if it would preseve them as it makes reading output a little difficult sometimes. Add Comment
[JIRA] [ec2-plugin] (JENKINS-32379) integrate with the 'config file provider' plugin
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-32379 integrate with the 'config file provider' plugin Issue Type: New Feature Assignee: Francis Upton Components: ec2-plugin Created: 10/Jan/16 4:59 PM Priority: Minor Reporter: Jae Gangemi it would be great if you could add support to allow managing init-script data via the config files provider plugin so a single script could be used across multiple instances, but updated only once. thanks!! Add Comment
[JIRA] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title Jae Gangemi commented on JENKINS-28238 Re: Github Plugin Failing to re-register for hooks yeah - that's what i'm missing. you'd think github would alert me to that fact, but they don't. this can be closed. i would like to make the suggestion that you update the wiki page to state that in addition to the hook permission needed, the user itself must also be an owner in github. unfortunate they don't offer another level of privs for this. my jenkins user is a machine user and "owner" isn't appropriate, but that's not your problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title Jae Gangemi updated an issue Jenkins / JENKINS-28238 Github Plugin Failing to re-register for hooks Change By: Jae Gangemi Attachment: ishot-2.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title Jae Gangemi commented on JENKINS-28238 Re: Github Plugin Failing to re-register for hooks i am using the plugin itself to create the token, so whatever it creates plus i manually add admin:org_hook. see the attached screenshot. one thing i was just thinking...what access level does this user need to have in github itself? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title Jae Gangemi commented on JENKINS-28238 Re: Github Plugin Failing to re-register for hooks i am having the same problem. Nov 04, 2015 8:41:42 PM WARNING org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafeFailed to add GitHub webhook for GitHubRepositoryName[host=github.com,username=condevops,repository=hello-world-jenkins] java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=condevops,repository=hello-world-jenkins] at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:231) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:151) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:147) at org.jenkinsci.plugins.github.util.misc.NullSafeFunction.apply(NullSafeFunction.java:18) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:648) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:647) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:119) at org.jenkinsci.plugins.github.util.FluentIterableWrapper.toList(FluentIterableWrapper.java:137) at org.jenkinsci.plugins.github.webhook.WebhookManager$1.run(WebhookManager.java:97) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) 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) this is a brand new jenkins setup w/ the following versions: jenkins: 1.636 git plugin: 2.4.0 git client: 1.19.0 github plugin: 1.14.0 my oauth token has the correct permissions and the verify credentials button indicates everything can connect. Add Comment
[JIRA] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title
Jae Gangemi edited a comment on JENKINS-28238
Re: Github Plugin Failing to re-register for hooks
i am having the same problem.{code}Nov 04, 2015 8:41:42 PM WARNING org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafeFailed to add GitHub webhook for GitHubRepositoryName[host=github.com,username=condevops,repository=hello-world-jenkins]java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=condevops,repository=hello-world-jenkins] at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:231) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:151) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:147) at org.jenkinsci.plugins.github.util.misc.NullSafeFunction.apply(NullSafeFunction.java:18) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:648) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:647) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:119) at org.jenkinsci.plugins.github.util.FluentIterableWrapper.toList(FluentIterableWrapper.java:137) at org.jenkinsci.plugins.github.webhook.WebhookManager$1.run(WebhookManager.java:97) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) 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){code}this is a brand new jenkins setup w/ the following versions:{code}jenkins: 1.636git plugin: 2.4.0git api: 1.69git client: 1.19.0github plugin: 1.14.0{code}my oauth token has the correct permissions and the verify credentials button indicates everything can connect.
Add Comment
This message was sent by Atlassian JIRA
[JIRA] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title
Jae Gangemi commented on JENKINS-28238
Re: Github Plugin Failing to re-register for hooks
i am also unable to set the build status at the end of the job
Setting commit status on GitHub for https://github.com/condevops/hello-world-jenkins/commit/9147bf95263836cd6bccfd1e7882ac7498e79ca6
ERROR: Step ‘Set build status on GitHub commit’ aborted due to exception:
java.io.FileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
at org.kohsuke.github.Requester.handleApiError(Requester.java:501)
at org.kohsuke.github.Requester._to(Requester.java:248)
at org.kohsuke.github.Requester.to(Requester.java:194)
at org.kohsuke.github.GHRepository.createCommitStatus(GHRepository.java:829)
at com.cloudbees.jenkins.GitHubCommitNotifier.updateCommitStatus(GitHubCommitNotifier.java:138)
at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:90)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1047)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671)
at hudson.model.Run.execute(Run.java:1766)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: java.io.FileNotFoundException: https://api.github.com/repos/condevops/hello-world-jenkins/statuses/9147bf95263836cd6bccfd1e7882ac7498e79ca6
at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:240)
at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210)
at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25)
at org.kohsuke.github.Requester.parse(Requester.java:458)
at org.kohsuke.github.Requester._to(Requester.java:227)
... 13 more
Finished: FAILURE
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title Jae Gangemi assigned an issue to Kanstantsin Shautsou Jenkins / JENKINS-28238 Github Plugin Failing to re-register for hooks Change By: Jae Gangemi Assignee: Richard Duarte Kanstantsin Shautsou Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks
Title: Message Title Jae Gangemi reopened an issue Jenkins / JENKINS-28238 Github Plugin Failing to re-register for hooks Change By: Jae Gangemi Status: Resolved Reopened Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
