[JIRA] (JENKINS-54468) Not applicable Branch Build Strategies are available in the Organization UI

2018-11-05 Thread r...@shamu.ch (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Ryan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54468  
 
 
  Not applicable Branch Build Strategies are available in the Organization UI   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 branch-api-plugin  
 
 
Created: 
 2018-11-05 16:22  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Manuel Ryan  
 

  
 
 
 
 

 
 The list of available branch build strategies for organizations always contains all strategies, independently of the SCMSource and / or project type. This is because the list of available strategies is loaded like this :  Which bypasses all the checks performed by BranchBuildStrategyDescriptor.all(project, sourceDescriptor).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-46851) Mercurial doesn't use credentials in Modern SCM for Shared Library

2018-04-11 Thread r...@shamu.ch (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Ryan commented on  JENKINS-46851  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Mercurial doesn't use credentials in Modern SCM for Shared Library   
 

  
 
 
 
 

 
 Same issue here, using "Legacy SCM" instead of "Modern SCM" solved my issue.  
 

  
 
 
 
 

 
 
 

 
 
 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-41657) workflow-cps-global-lib not compatible with mercurial

2017-02-23 Thread r...@shamu.ch (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Ryan commented on  JENKINS-41657  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: workflow-cps-global-lib not compatible with mercurial   
 

  
 
 
 
 

 
 Created PR #99 in the mercurial plugin to allow filling credential ids from the admin panel (https://github.com/jenkinsci/mercurial-plugin/pull/99)  
 

  
 
 
 
 

 
 
 

 
 
 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-35233) Maven plugin + custom build environment, POM parsing happens outside of container

2017-02-22 Thread r...@shamu.ch (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Ryan commented on  JENKINS-35233  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Maven plugin + custom build environment, POM parsing happens outside of container   
 

  
 
 
 
 

 
 For anyone stumbling on this issue : My workaround was to switch to the Kubernetes plugin instead of the "custom-build-environment" plugin.  
 

  
 
 
 
 

 
 
 

 
 
 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-41657) workflow-cps-global-lib not compatible with mercurial

2017-02-02 Thread r...@shamu.ch (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Ryan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41657  
 
 
  workflow-cps-global-lib not compatible with mercurial   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 workflow-cps-global-lib-plugin  
 
 
Created: 
 2017/Feb/02 1:07 PM  
 
 
Environment: 
 Jenkins 2.32.1  workflow-cps-global-lib-plugin 2.5  scm api 1.3  mercurial plugin 1.57  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Manuel Ryan  
 

  
 
 
 
 

 
 I'm trying to use the workflow-cps-global-lib plugin with the mercurial SCM (legacy mode) The dropdown to select the credentials for the mercurial checkout of the library doesn't contain the username/password credentials that I have configured globally. I tried configuring the credentialsId manually in the org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml file and "reload from disk" but it seems it was ignored when trying to import the library I get Authentication required.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-23571) Option to control repos cache path directory

2016-11-25 Thread r...@shamu.ch (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Ryan commented on  JENKINS-23571  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Option to control repos cache path directory   
 

  
 
 
 
 

 
 I have the same need, I manage a lot of jenkins masters and I want the hgcache directory to be outside of $JENKINS_HOME for storage and backup reasons. I have implemented this feature in the following PR : https://github.com/jenkinsci/mercurial-plugin/pull/91  
 

  
 
 
 
 

 
 
 

 
 
 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

2016-10-25 Thread r...@shamu.ch (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Ryan commented on  JENKINS-39014  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: expose underlying host ip as environment variable   
 

  
 
 
 
 

 
 I have a similar situation and solved it by attaching the container running the tests and the database container to the same docker network bridge, then docker itself will provide you with container DNS on that bridge that you can use in your tests to address the DB container. (documentation on this feature here : https://docs.docker.com/engine/userguide/networking/configure-dns/) It could look like this inside the test container :  // Spin up the mysql db for tests docker run --network="it-test-network" --network-alias="mysql" mysql // Attach the current container (hostname is the container ID) to the same network docker network attach $(hostname) it-test-network // let docker's DNS work it's magic. ping mysql Limitation : this only works if both containers run on the same docker host. This seems to be your case since you spin up mysql on the shared docker socket.  
 

  
 
 
 
 

 
 
 

 
 
 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-29674) Maven project not supported by the build environment plugin

2016-10-25 Thread r...@shamu.ch (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Ryan commented on  JENKINS-29674  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Maven project not supported by the build environment plugin   
 

  
 
 
 
 

 
 The maven plugin 2.14 which was released 5 days ago contains your changes from maven-plugin PR 51 and maven-interceptors PR 8 right ? Can you re-open this issue and see if you can make a version of the custom-build-environment plugin that is compatible with maven-plugin 2.14 ?  
 

  
 
 
 
 

 
 
 

 
 
 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-36769) Cannot override /tmp volume mount

2016-10-25 Thread r...@shamu.ch (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Ryan commented on  JENKINS-36769  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot override /tmp volume mount   
 

  
 
 
 
 

 
 Mounting /tmp is required for executing shell build steps, the shell script is written in /tmp by the master/slave and read from the build container, if you don't share it directly, you'll have a FileNotFound.  
 

  
 
 
 
 

 
 
 

 
 
 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] [docker-custom-build-environment-plugin] (JENKINS-32542) Maven project failed with "Connection refused" when built in a docker Container

2016-05-31 Thread r...@shamu.ch (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Ryan commented on  JENKINS-32542 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Maven project failed with "Connection refused" when built in a docker Container  
 
 
 
 
 
 
 
 
 
 
It all boils down to the "getDocker0" method in the custom-build-plugin. We should not assume that the address of the jenkins (master or slave) is the default gateway of the container it starts. The basic example is jenkins running in a container with a shared docker socket. 
I think a portable solution could be to allow master/slave provisionners to specify and environment variable (for the master/slave process) with the value computed depending on their networking environment (there are so many different scenarios, we can give sensible defaults, but we also need to allow full customization).  
The environment variable could be something like JENKINS_MAVEN_PLUGIN_HOST. I'll try to submit a PR tomorrow for 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] [docker-custom-build-environment-plugin] (JENKINS-32542) Maven project failed with "Connection refused" when built in a docker Container

2016-05-31 Thread r...@shamu.ch (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Ryan commented on  JENKINS-32542 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Maven project failed with "Connection refused" when built in a docker Container  
 
 
 
 
 
 
 
 
 
 
I'm using the kubernetes plugin to provision fungible slaves in a cluster for each build and I have this issue too. 
Maybe the "dockerhost" hostname should actually be "jenkinshost" and be obtained by running somethig like "hostname -i" on the jenkins host performing the build (the slave container in my case) instead of the "ip route in an alpine:3.2 container" technique. 
Some other issues remain as the port needs to be exposed in the slave pod. 
 

The kubernetes plugin needs to be able to specify port exposition in slave templates
 

The jenkins-maven plugin needs to support using a fixed port for the jvm agent -> build host connection. (this would cause collisions in most cases, but not when using the kubernetes plugin as each build has it's own IP address).
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-35233) Maven plugin + custom build environment, POM parsing happens outside of container

2016-05-31 Thread r...@shamu.ch (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Ryan created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35233 
 
 
 
  Maven plugin + custom build environment, POM parsing happens outside of container  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 maven-plugin 
 
 
 

Created:
 

 2016/May/31 9:20 AM 
 
 
 

Environment:
 

 jenkins 2.3, maven plugin 2.12.1, Custom build environment 1.6.5 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Manuel Ryan 
 
 
 
 
 
 
 
 
 
 
When building a maven job inside a container with the custom build environment plugin, the maven plugin parses the POMs outside of the build environment container. 
Because of this, I had to install and configure maven on my build host instances (and I fear I may have maven version issues because of that). 
Ideally, the integration between the two plugins should be improved to :  
 

Skip checks that maven is configured as a global tool when the build is done in a container
 

Perform all maven plugin operations (verify that the $MAVEN_HOME is valid, parse poms, etc...) inside the custom build environment

[JIRA] [docker-custom-build-environment-plugin] (JENKINS-29194) doesn't work with remote docker servers

2016-05-25 Thread r...@shamu.ch (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Ryan commented on  JENKINS-29194 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: doesn't work with remote docker servers  
 
 
 
 
 
 
 
 
 
 
you can mount /tmp between your slave and your build image  it's very ugly, but it works ! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [docker-custom-build-environment-plugin] (JENKINS-33232) Not working in internal network.

2016-05-09 Thread r...@shamu.ch (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Ryan commented on  JENKINS-33232 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Not working in internal network.  
 
 
 
 
 
 
 
 
 
 
I'm having this issue too ! 
I think a clean solution would be to add a configuration field to allow users to choose an image containing the "true" and "ip" binaries (with a default value of "alpine:3.2") 
That way we could push the alipne:3.2 image to our private registry and tell the plugin to use "my.private.registry/alpine:3.2" instead of "alpine:3.2" 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [docker-custom-build-environment-plugin] (JENKINS-34591) Cannot use a private repository as image source

2016-05-09 Thread r...@shamu.ch (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Ryan commented on  JENKINS-34591 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot use a private repository as image source  
 
 
 
 
 
 
 
 
 
 
Duplicate of JENKINS-33232 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.