Try to check the following:
- try to monitor the folder - who uses the folder (sysinternals may contain
something useful)
- disable antivirus or similar software (if possible)
- print content of the folder before git checkout (is it pipeline job or
freestyle?)
- check network connectivity (i.e.
I resolved my issue by below 2 modifications:
1. Change to the Gerrit REST API URL:
*http://gerrit.xxx.com/a/changes/?q=status:merged+branch:master*
2. auth.gitBasicAuth set to true
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To
When you are trying to *copy* things you will generally find you have
missed something, jobs with secrets won;t work as Jenkins will no longer be
able to decrypt the secret etc etc...
Given the error is around authentication I would hazard a guess that this
is the cause of your woes.
did some
I need this also so any suggestions on how to get it working would be
appreciated.
We are automating publishing and need to pass in npm tokens, user name,
passwords, etc in order for publishing to be successful.
On Wednesday, June 14, 2017 at 6:15:34 PM UTC-5, Cuong Tran wrote:
>
> Why?
>
>
Hello,
I am currently in the middle of upgrading from an older version of Jenkins
(1.534) in a standalone configuration, to the latest version (2.65) with a
Master / Slave Node configuration. I am basically standing up the new
Jenkins Master / Slave Node servers and using the job import plugin
If you look at https://jenkins.io/download/lts/ there is a link to
https://jenkins.io/event-calendar/ where you can see the schedule.
/Jacob
On 2017-06-19 17:49, Tammy Osborn wrote:
I happened to see some info in another thread for this group that the
next LTS release is 2.60.1
But I
>From the link:
Description
Sometimes, the git init-command fails because of the .git/config-file is
non-writeable.
Logging into the slave, there seems to be nothing wrong with the permissions on
the file.
When it is good, it just inits the repo.
12:33:36 Started by GitLab push by the_persion
I happened to see some info in another thread for this group that the next
LTS release is 2.60.1
But I couldn't find that info on any of the LTS Wiki pages. I also would
like to find out the general timeframe for the next release.
Where can I go to get up-to-date info on the LTS schedule?
Please share your job logs
On Monday, June 19, 2017 at 10:30:51 AM UTC+3, xJom wrote:
>
> Hi!
>
> Using Jenkins 2.46.1 LTS on an Ubuntu server, and a virtual Windows slave,
> we sometime get an error when initializing the git repo (from GitLab on the
> same Ubuntu server).
>
> Originally, we
I have a working Jenkins v2.19 instance. I have a main pipeline job that
references a Jenkinsfile in a BitBucket repo, accessed through a ssh url.
The Jenkinsfile references a global shared library, also stored in
BitBucket with a ssh url.
I'm working with someone who's trying to upgrade me
You might get more response if you describe a bit more what you are looking
for.
On Fri, Jun 16, 2017 at 8:10 AM Evgueni Kolossov
wrote:
> Hi,
>
> Does anybody interested in contract to upgrade existing Jenkins plug-in?
>
> --
> You received this message because you are
Hi Don,
You can add yourself (though you are probably added now that you are
allowed to post), by using the Google Groups web interface. If you aren't
receiving all the messages, you can change your settings on Google Groups.
Thanks,
Alex
On Thu, Jun 15, 2017 at 7:23 AM Don Robbins
Hello,
I am putting the vSphere Cloud Plugin up for adoption - would any one like
ownership of it? If so please contact me directly via email.
Wiki page: https://wiki.jenkins-ci.org/display/JENKINS/vSphere+Cloud+Plugin
Source: https://github.com/jenkinsci/vsphere-cloud-plugin
Jason Swager
--
> On 18. Jun 2017, at 07:43, Seb M wrote:
>
> So this does not really seam to work? Or is there some error in my syntax?
Tri triple-single-quoted strings or escaping the $ -- right now, it's looking
for a DSL variable "CHANGES" as it evaluates the ${CHANGES, …}
Hi!
Using Jenkins 2.46.1 LTS on an Ubuntu server, and a virtual Windows slave,
we sometime get an error when initializing the git repo (from GitLab on the
same Ubuntu server).
Originally, we thought it was an issue with the
Git-plugin: https://issues.jenkins-ci.org/browse/JENKINS-41169
We
15 matches
Mail list logo