o 2.x?
Mark
/mde/
On Wednesday, May 25, 2016 at 1:56:07 PM UTC-7, Mark Eggers wrote:
>
> Hi,
>
> I'm trying to reorganize a bunch of Groovy scripts with Scriptler, and I
> would like to use the git repository.
>
> My environment:
>
> CentOS 6.8 64 bit
> JRE 1.
Hi,
I'm trying to reorganize a bunch of Groovy scripts with Scriptler, and I
would like to use the git repository.
My environment:
CentOS 6.8 64 bit
JRE 1.8.0_92 (Oracle)
git 1.7.12.4 (rpmforge)
Apache HTTPD 2.2.15-53 (CentOS)
mod_jk 1.2.41 (ASF)
Tomcat 8.0.33 (ASF)
Jenkins 2.6 (upgraded from
;
> On 12.04.2016, at 01:09, Mark Eggers >
> wrote:
>
> > If I remove the third party update center on the test Jenkins, then
> Jenkins acts as if there are no update sites available.
>
> If by that you mean that you clear the form field in Manage Plugins ยป
> Advanced, d
I thought that I had two identical Jenkins 1.656 installations (production
and test), running on Tomcat 7.0.68.
However on the test system I'm not able to get updates from the default
update center (a third party update center works).
When I look at the logs of the failing system, there is no l
skip this for the
>>> meanwhile. Also, could you please verify that your installation passes the
>>> 'curl' test?
>>> >
>>> > curl -iL -e https://hostname/jenkins/manage
>>> https://hostname/jenkins/administrativeMonitor/
I've not seen this.
For my Jenkins URL:
http://[hostname]/jenkins/
In my uriworker.properties file:
/jenkins|/*=[workername]
Then in the Apache HTTPD host that manages Jenkins:
JkMountFile conf.d/uriworkermap.properties
There's a good base workers.properties configuration example in conf
su
ith Jenkins 1.600+. Are you experiencing any problems?
> Because it's only incompatible with earlier Jenkins versions.
>
> On 04.03.2015, at 17:09, Mark Eggers >
> wrote:
>
> > I just rolled out 1.601 on two machines. It appears that the matrix
> project plugin version
I just rolled out 1.601 on two machines. It appears that the matrix project
plugin version 1.4.1 is back. On one machine I attempted to both unpin and
roll back the plugin version to 1.3. After a restart the plugin version
remains at 1.4.1. I now no longer have the option of downgrading the
plu
I am seeing this as well. However, one Jenkins server works flawlessly,
while the other one does not.
The only difference is that the impacted server is using subversion 1.8,
while the operational server is using subversion 1.6.
There are some other issues as well - I'll try to document them w
On Friday, December 19, 2014 8:55:43 AM UTC-8, MoBarger wrote:
>
> Hi - working on implementing the latest LTS update, we are encountering
> the reverse proxy error when going to Jenkins admin page. Is it possible to
> resolve this issue using mod_jk configuration we currently use or is the
> o
To expand on what Bertram wrote:
It appears that the Jenkins Maven release plugin sets a few parameters:
MVN_RELEASE_VERSION
MVN_DEV_VERSION
MVN_ISDRYRUN
I've not tried this, but it may be possible to use this information coupled
with the
email extension plugin to send the appropriate message.
This appears to be the following issue:
https://issues.jenkins-ci.org/browse/JENKINS-19564
My initial take on this is that it's a Cargo issue with parallel deployment.
Mark
/mde/
On Monday, August 4, 2014 6:23:40 PM UTC-7, Mark Eggers wrote:
>
> Further followup:
>
> It seem
deggers.org:8080/manager/text/undeploy?path=/ConsumeIt&version=13'
works as expected, and then the next Jenkins deployment works as well.
Maybe this is an enhancement request?
Mark
/mde/
On Monday, August 4, 2014 5:21:18 PM UTC-7, Mark Eggers wrote:
>
> Never mind, I figured it ou
application in NetBeans, and still have versioned applications on Tomcat.
However, that's a Maven question.
Sorry for the noise.
Mark
/mde/
On Monday, August 4, 2014 4:55:25 PM UTC-7, Mark Eggers wrote:
>
> Hi,
>
> I'm trying to use the deploy plugin to deploy to a Tomcat 7.0.55 se
Hi,
I'm trying to use the deploy plugin to deploy to a Tomcat 7.0.55 server.
I'm trying to use versioned WAR files (appName##number.war).
I can create the WAR file easily by passing BUILD_NUMBER in on the command line
and then using a property within finalName.
The first problem came when specif
15 matches
Mail list logo
