I don't know if I fully understand your question... but here is something I
did to solve getting scripts for execution in RepoA from repo's B,C,D... I
now know the specific directories to execute the scripts from and the files
that needed to be updated for Puppet.
If you find a better way or
(replies inline)
On Fri, 29 Sep 2017, dandeliondodgeball wrote:
> Pipeline 1 just runs a script, and has the "Workspace" icon.
>
> Pipeline 2 runs a Jenkinsfile and doesn't have the "Workspace" icon.
>
> What I mean by "Workspace" icon.
>
>
Pipeline 1 just runs a script, and has the "Workspace" icon.
Pipeline 2 runs a Jenkinsfile and doesn't have the "Workspace" icon.
What I mean by "Workspace" icon.
Maybe I am not understanding shared libraries. I have another repo, in
which there are python scripts I need to call to be able to build the repo
for which I have the pipeline created. So I make pipeline A for repo B,
but I need to call scripts in repo C to build. It looked like shared
I think some of the help for the "Recipients" list needs to be clariefied.
I hadn't realized that the general "Recipients" list was used in ADDITION
to any recipients for specific trigger emails.
--
CasaDelGato Sensible Email package:
https://sourceforge.net/projects/sensibleemail/
--
You
https://github.com/Praqma/JenkinsAsCodeReference is an interesting
initiative, not perfect though.
it can anyway give you some idea about what and how to configure.
I'm currently working on a more "elegant" and easier to maintain solution,
will announce it somewhere here for sure when it's ready
Hello folks,
I have a peculiar issue and based on my testing it seems to be a jenkins
issue.
Setup: An AWS EC2 instance running Jenkins behind nginx proxy
Installed with packer and ansible
Jobs:
1. git job that pulls the anible.yml playbook from aws codecommit (It
installs PH and httpd24)
2.
Did you manage to make it work?
because I do it differently, usually:
- download slave-agent.jnlp from agent page - I think it's under this
'launch via web' button, or something, I don't remember what it says :)
- open a command window with "Run as Administrator".
- change directory to the
docker.inside NEED some way to run a docker container in some "wait" mode,
so the use of the `cat` command.
if your entrypoint script do follow docker recommendations it *should* detect
use of such a command and enventually execute it, but real world experience
demonstrated many people don't
On 29.09.2017 09:11, Dirk Heinrichs wrote:
This looks to me as if you were trying to run the git commands from an
"Execute Windows Batch" step in your Jenkins job. It's far easier to
simply use the Git plugin to do the job together with the SSH key you
provided to Jenkins via "Manage
https://issues.jenkins-ci.org/browse/JENKINS-39748
On Thursday, 28 September 2017 18:49:04 UTC+8, Eric Tan wrote:
>
> Hi,
>
> Is there a way to prevent Jenkin from overriding the entrypoint specified
> in the container image?
> As shown below in the console output, Jenkins adds "*--entrypoint
Am 28.09.2017 um 16:54 schrieb Andreas Tscharner:
> Hello World,
>
> I have the following setup:
>
> git Server: Debian Linux 9.1
> Jenkins master: Debian Linux 9.1
> Jenkins agent: Windows 7
>
> I created a user on the git server for building, it is called "build".
> I also have created a ssh
I think you are missing the volume mapping:
-v $HOST_VOLUME:/var/jenkins_home
On Friday, 29 September 2017 11:06:47 UTC+8, jorge alarcon wrote:
>
> Hello everyone,
> I am porting some old code I had for jenkins, version 1.X.X. For this I
> had a Dockerfile that looked like this:
>
> FROM
On 28.09.2017 17:12, Mark Waite wrote:
I don't use putty and plink in my Windows based test setup for the git
plugin. Can you share the key reasons you chose those non-default
installation options?
IMHO PuTTY is THE ssh client for Windows (first hit with Google ("ssh
for Windows"), used
14 matches
Mail list logo
