Hello All,
Thank you very much!!
After removing the target and work directories and re-runing Jenkins, the
error doesn't appear.
Thank you again!!
On Thursday, 11 June 2015 03:40:12 UTC+5:30, Jesse Glick wrote:
>
> On Wed, Jun 10, 2015 at 9:00 AM, Daniel Beck > wrote:
> > Make sure you don
First sorry for posting the same/similar content multiple times in this
thread. That was because for some reason my post didn't show up so I
reposted several times. Now all the repeated posts show up.
I am not sure whether docker-build-step plugin is affected by that. Is
docker-build-step plugi
Hi Roman,
Thanks for pointers. I looking something which uses
csv for data.
On Wednesday, 10 June 2015 11:04:02 UTC+5:30, abhishek gupta wrote:
>
> Hi,
>
>In our company we have centralized Jenkins setup
> ,because of it we are keeping less than 5 buil
So there was some grand experiment with docker plugins that we did
internally at CloudBees. There were some plugins moved refactored a bit and
I was just asking if part of the result of that affected the
docker-build-step plugin.
On 8 June 2015 at 07:18, Wei Zheng wrote:
> Hi, Stephen:
>
> I am
I know I am somewhat new around here, but here is my opinion for whatever it is
worth.
I can definitely see value in being able to determine whether or not a plugin
is maintained, especially for when somebody is asking to be able to commit to
it. I do not think the model proposed would provide
On 11.06.2015, at 00:01, Daniel Beck wrote:
> This would also mess with updates to installed plugins after e.g. a core
> update.
Or even out of the box. Subversion Plugin, Javadoc Plugin, Ant Plugin,
Translation Assistance Plugin, ... don't look like they currently qualify for
out-of-attic s
On Wed, Jun 10, 2015 at 9:00 AM, Daniel Beck wrote:
> Make sure you don't have incompatible versions of these plugins manually
> installed in your work directory.
To be sure:
rm -rf target work
Possibly you installed matrix-project 1.4.1 in a previous session and
forgot about it. 1.580.3 canno
On Wed, Jun 10, 2015 at 1:53 AM, Kishore RP wrote:
> Does it provide real time update of tests like the way label based mechanism
> of blinking dots
Not quite sure I followed that, but: Workflow does not currently
provide a replacement for the UI aspect of matrix-project. It is under
considerati
On 10.06.2015, at 22:05, James Nord wrote:
> I would go one further and aswell as the metadata, create an "attic" update
> center akin to the "experimental" UC.
No way. I use quite a few plugins that haven't seen updates in years and work
well, better than several maintained plugins I could m
Hi,
I have made changes regarding its artifactId and a few other places related
to its name.
Here is my answer to Stephen and Jesse's questions after some investigation:
1. This proposed plugin is compatible with docker-commons-plugin, i.e.
when docker-commons-plugin looks for credential
Hi, Stephen:
I do not have all the context to understand your question to James/Oleg.
But I cold clarify a bit on the plugin I am proposing:
This plugin is a credential provider that provides credentials that can be
used to authenticate against Google Container Registry, and nothing more.
So t
Hi,
I have made changes to the artifact ID and other places related to the
plugin's names.
Regarding Stephen and Jesse's questions about integration with
docker-commons-plugin, this is my answer after investigation:
The change need to be made should be in docker-build-step-plugin. I have
made
Hi,
I have made changes regarding the artifactId and other places related to
name.
Regarding Stephen and Jessen's questions on integration with
docker-commons-plugin, here is my answer after investigation:
The change need to be made in docker-build-step-plugin, not in this plugin.
I have made
Hi,
I have made changes regarding its artifactId and a few other places related
to its name.
Here is my answer to Stephen and Jesse's questions after some investigation:
1. This proposed plugin is compatible with docker-commons-plugin, i.e.
when docker-commons-plugin looks for credential
Hi,
I have made changes regarding its artifactId and a few other places related
to its name.
Here is my answer to Stephen and Jesse's questions after some investigation:
1. This proposed plugin is compatible with docker-commons-plugin, i.e.
when docker-commons-plugin looks for credential
Hi,
I have made changes regarding its artifactId and a few other places related
to its name.
Here is my answer to Stephen and Jesse's questions after some investigation:
1. This proposed plugin is compatible with docker-commons-plugin, i.e.
when docker-commons-plugin looks for credential
Hi,
I have made changes regarding its artifactId and a few other places related
to its name.
Here is my answer to Stephen and Jesse's questions after some investigation:
1. This proposed plugin is compatible with docker-commons-plugin, i.e.
when docker-commons-plugin looks for credential
Hi,
I have made changes regarding its artifactId and a few other places related
to its name.
Here is my answer to Stephen and Jesse's questions after some investigation:
1. This proposed plugin is compatible with docker-commons-plugin, i.e.
when docker-commons-plugin looks for credential
Hi,
I have made changes regarding its artifactId and a few other places related
to its name.
Here is my answer to Stephen and Jesse's questions after some investigation:
1. This proposed plugin is compatible with docker-commons-plugin, i.e.
when docker-commons-plugin looks for credential
Hi, Stephen:
I am not sure why you asked whether build-step get re-positioned. The
plugin I am proposing is simply a credential provider when authentication
against Google Container Registry is needed. It does not perform any docker
actions, so it needs to work with a plugin like docker-build-s
Hi, Stephen:
I do not have all the context to understand your question below about the
"re-position", but here is a little more I want to say about the plugin I
want to propose:
This plugin is a credential provider (which provides credentials when
authentication against Google Container Registr
Hi,
I have made changes regarding its artifactId and a few other places related
to its name.
Here is my answer to Stephen and Jesse's questions after some investigation:
1. This proposed plugin is compatible with docker-commons-plugin, i.e.
when docker-commons-plugin looks for credential
My ones are:
JENKINS-28690 (fix merged to trunk)
JENKINS-28840 (expect a fix tomorrow)
JENKINS-28844 (pull request under review)
Of these 28690 and 28840 I view as critical to pick up in 1.609.2 whereas
28844 is a really really really nice to have (pretty please with catnip)
I suspect that we ma
I would go one further and aswell as the metadata, create an "attic" update
center akin to the "experimental" UC.
It's sometimes daunting for a new admin to find that one plugin that may do
what he needs from the 1000+ listed...
On Tuesday, 9 June 2015 11:57:47 UTC+1, Stephen Connolly wrote:
>
You are free to pick any issue and propose PR, then wait some time for
somebodies review. As first steps i think it the most common way.
On Wednesday, June 10, 2015 at 7:27:31 PM UTC+3, Mayur Barge wrote:
>
> Hello Team,
> I have started using Jenkins two months back and would like to
>
I think I have three issues that should go in despite not meeting the
standard criteria. In two cases the change is small, low risk and I have
analysed the change for impact.
The third is a remoting change I am currently working to get merged... I'd
like if it can be included butay be able to hav
Yeah, that makes sense.
There's a plugin for standalone install of JIRA for that and an old ticket:
https://jira.atlassian.com/browse/JRA-3501
Thanks for the info.
Regards,
Radek
On Wed, Jun 10, 2015 at 1:19 PM, Daniel Beck wrote:
> We removed these a while back. 'current' was the only valid
We removed these a while back. 'current' was the only valid value for years,
and the test of having all versions of all plugins didn't go well,
autocompletion completely broke.
Right now, the best option to indicate which release a fix will be in is
probably in a comment.
On 10.06.2015, at 19:
Hi Richard,
Thanks, I sorted it out with Olivier.
Is there any chance to get a "Fix Version" field in the Jenkins JIRA?
Regards,
Radek Antoniuk
On Tue, Jun 9, 2015 at 11:38 PM, Richard Bywater wrote:
> To confirm, have you attempted to contact the current maintainer?
>
> Richard
>
> On 3:35PM
Hello Team,
I have started using Jenkins two months back and would like to
contribute to core project. Can someone please guild me in this ? I
acknowledge that preparing environment for building jenkins, forking
repository to contribute through pull request are basic ones.
Thanks,
Mayur
Hey,
The related fix can be found here:
https://github.com/jenkinsci/jenkins/issues/1725
On Wednesday, June 10, 2015 at 6:20:23 PM UTC+3, Daniel Beck wrote:
>
> JENKINS-27289 has a partial fix in PR 1598 that qualifies, but it's not
> marked Resolved since the fix is apparently incomplete. How sh
JENKINS-27289 has a partial fix in PR 1598 that qualifies, but it's not marked
Resolved since the fix is apparently incomplete. How should we handle that one?
https://issues.jenkins-ci.org/browse/JENKINS-27289
https://github.com/jenkinsci/jenkins/pull/1598
On 08.06.2015, at 22:29, oliver gondža
On 10.06.2015, at 14:38, Vinodhini Vijay wrote:
> Our concern is that if we use this LTS version: 1.580.1/2/3 for our plugin
> development,and also in testservers, we might not be able to use some good
> features of Jenkins like Matrix Project, etc.. as it might be disabled.
>
> Any advice (o
Hello Mr.Beck,
Our plugin doesn't depend on any of the plugins (
*matrix-auth,windows-slaves,antisamy-markup-formatter,matrix-project,script-security*).
Our concern is that if we use this LTS version: 1.580.1/2/3 for our plugin
development,and also in testservers, we might not be able to use
Is your plugin depending on any of the plugins mentioned in the error messages,
and if so, which versions?
On 10.06.2015, at 13:30, Vinodhini Vijay wrote:
>
>
> Hello All,
>
> We are using Jenkins 1.580.3 LTS version for our plugin development. While
> starting Jenkins via mvn hpi:run, we a
Hello All,
We are using Jenkins 1.580.3 LTS version for our plugin development. While
starting Jenkins via mvn hpi:run, we are getting the below error:
Jun 10, 2015 4:30:11 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Jun 10, 2015 4:30:32 PM hudson.PluginManager$1$3
I know this from starting . I have studied the two plugins i mentioned.
then only i am asking this question Because i am getting values as strings
and integers only
On Monday, 8 June 2015 22:29:42 UTC+5:30, Ullrich Hafner wrote:
>
>
> Am 08.06.2015 um 13:23 schrieb Saurabh Garg >:
>
> How can I
@Stephen
+1 for PR as this shows which plugins have no maintainers and plugins in
the attic space can possibly be hidden in the available plugins (yes, 1000+
plugins is too much to find which plugins can be useful).
@Kanstantsin
Fortunately, the numbers of current installations by plugins are al
Hi,
For free graphs I used
https://wiki.jenkins-ci.org/display/JENKINS/dbCharts+Plugin
--
Thanks,
Roman
On Tue, 2015-06-09 at 22:34 -0700, abhishek gupta wrote:
> Hi,
>In our company we have centralized Jenkins setup
> ,because of it we are keeping less than 5 build per job.
39 matches
Mail list logo
