1.1.1 deployed although Maven failed with the below (after clearly
uploading successfully) , will check back tomorrow.
[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on
project ez-templates: Failed to deploy artifacts: Could not tr
Hi,
I need to create a new user account on Jenkins. While trying to create an
account from *jenkins-ci.org/account/signup* I got the below message.
*“Due to the spam problem, we need additional verification for your sign-up
request. Please contact “jenkinsci-dev@googlegroups.com”.*
Hi Jenkins Team,
We are moving from Jenkins 1.580.3 to Jenkins Jenkins 1.625.2.
The* Build Summary* is not coming in proper alignment in Jenkins 1.625.2
When we are running combination of plugins then Build Summary is not coming
in proper alignment.
I attached the screen shot for the same.
Pl
Hi Jenkins Team,
We are moving from Jenkins 1.580.3 to Jenkins Jenkins 1.625.2.
The* Build Summary* is not coming in proper alignment in Jenkins 1.625.2
When we are running combination of plugins then Build Summary is not coming
in proper alignment.
I attached the screen shot for the same.
Pl
What makes you think this question is appropriate for the developers list?
On 17.12.2015, at 11:39, Shakir Ali wrote:
> Hi Jenkins Team,
>
> We are moving from Jenkins 1.580.3 to Jenkins Jenkins 1.625.2.
>
> The Build Summary is not coming in proper alignment in Jenkins 1.625.2
>
> When we ar
And sending it 3 times in dev and users list in less than 30 minutes won't
give you more attention
You have to remember that we are a distributed and asynchronous team thus
it may take some hours or days to have a response
Best regards
On Thu, Dec 17, 2015 at 11:42 AM, Daniel Beck wrote:
> What
Please use the issue tracker for such reports.
> Am 17.12.2015 um 11:36 schrieb Shakir Ali :
>
> Hi Jenkins Team,
>
> We are moving from Jenkins 1.580.3 to Jenkins Jenkins 1.625.2.
>
> The Build Summary is not coming in proper alignment in Jenkins 1.625.2
>
> When we are running combination of
+1 thanks and congrats Emeric!
Gonna use it to make the plugins I maintain disappear from this list (using
deprecated code) :-).
2015-12-14 13:49 GMT+01:00 Andrew Bayer :
> Yeah. This is really fascinating stuff - thanks for the work!
>
>
> On Monday, December 14, 2015, Oleg Nenashev
> wrote:
>
Hello,
I can see that in this s3 plugin, there is a lot of open PR. Maybe Michael
Watt might be overloaded on the subject. I'd like to offer my help to sort
the PR, merge and release the plugin.
For example, it is not possible for the moment to use it with copyartifact
more recent that 1.36. This
IIUC, this is somehow a similar things of what Google has been doing to
scale Jenkins, isn't it?
I've not checked, but read that what Google did is also available in
open-source (kk's tweet IIRC), should it be coordinated?
My 2 cents
2015-12-15 17:20 GMT+01:00 Surya Gaddipati :
> Hi All,
>
> Is
Seems to me that though hosting plugins come with very few
restrictions/rules, it's sad to find cases like here: It'll more complex
for users, less unified.
And as Daniel said, hosting has never actually been designed to use GH
issues, and the wiki page macro will just point to something wrong...
Hi,
The last release (1.0.4) of job-node-stalker-plugin has been tagged but not
properly released through Maven. So it's not available in Artifactory and
the POM is still at 1.0.4-SNAPSHOT. I pinged the maintainer in September
(see below) but got no response. Can I get commit access to
job-node-st
What is the typical turn around on creating the project? It's a busy time
of year, I just want to ensure that this request did not get lost in the
shuffle.
On Monday, December 14, 2015 at 2:13:58 PM UTC-5, Inky Sea wrote:
>
> GitHub repository URL :
> https://github.com/inkysea/vmware-vrealiz
Hi Oleg and Wolfgang,
thanks Wolfgang for your answer.
We got Dynatrace already in the Plugin title: "Performance Signature with
Dynatrace Plugin".
Do we have to update the artifactId, since we use plugin in several
environments?
Kind regards,
Raphael
Am Montag, 23. November 2015 10:38:08 UTC
Hi Adrien,
Thanks for the proposal: the process is to ping the current maintainer(s)
to get what they think.
It's indeed up to each maintainer to provide approval (or consider the
plugin unmaintained when no answer for some time).
Not sure what should be done for plugins with PR, but w/o someone
The plugin ID should ideally be close to the display name (as it's used e.g. in
JIRA as component), and obvious about what it is. So 'dynatrace' should be in
there.
On 17.12.2015, at 16:33, Raphael Pionke wrote:
> Hi Oleg and Wolfgang,
>
> thanks Wolfgang for your answer.
> We got Dynatrace a
I don't know enough about it, but just to check: is this a product really
different from VMWare/VSphere (both exist)?
Shouldn't/Couldn't it be integrated in one existing plugin as an extension
or something?
(Not saying it should, again, just for the record trying to get your
take/opinion about it
Heh, Yea probably. I saw the google talk on youtube.
Which basically amounted to, "we do x,y,z to make jenkins scale but none of
it is open source so you'd have to take our word for it" . Okay .
Surya
On Tuesday, December 15, 2015 at 10:20:31 AM UTC-6, Surya Gaddipati wrote:
>
> Hi All,
>
> Is
Baptiste,
yes if it can help having better plugins.
-- Adrien
Le jeu. 17 déc. 2015 à 16:35, Baptiste Mathus a écrit :
> Hi Adrien,
>
> Thanks for the proposal: the process is to ping the current maintainer(s)
> to get what they think.
> It's indeed up to each maintainer to provide approval (or
VMware's vRealize Automation (vRA) is a cloud management platform that
allows provisioning on various type of infrastructure. For example, vRA
can provision workloads to vSphere, HyperV, AWS, Azure, etc...
The other VMware/VSphere plugins are for different products in the VMware
suite. Atte
Done!
On 17/12/15 15:31, Daniel Spilker wrote:
> Hi,
>
> The last release (1.0.4) of job-node-stalker-plugin has been tagged but
> not properly released through Maven. So it's not available in
> Artifactory and the POM is still at 1.0.4-SNAPSHOT. I pinged the
> maintainer in September (see below
Fair enough.
If you could remove the "-plugin" suffix from your artifact ID, that
would be great (it's listed in the prerequisites here:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites)
Thanks,
Chris
On 17/12/15 18:46, Inky Sea wrote:
> VMware's vRealize
Ok. I'll hold off on the Issues issue and see how it goes.
ez-templates-1.1.1 has *still* not emerged into the update center!
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it
I updated the ID to vmware-vrealize-automation
https://github.com/inkysea/vmware-vrealize-automation
On Thursday, December 17, 2015 at 2:58:05 PM UTC-5, Christopher wrote:
>
> Fair enough.
>
> If you could remove the "-plugin" suffix from your artifact ID, that
> would be great (it's listed in
Hi,
After a great contribution of @kinow , I was able to understand and run my
plugin on slave machines. \o/
There is only one issue: how is the *right *way to get System variables
from a slave machine?
calling *Computer.currentComputer().getEnvironment();* outside Callable -
I get varia
I've seen it take up to 24 hours...
On Thu, Dec 17, 2015 at 1:06 PM Marc Carter wrote:
> Ok. I'll hold off on the Issues issue and see how it goes.
>
> ez-templates-1.1.1 has *still* not emerged into the update center!
>
> --
> You received this message because you are subscribed to the Google G
IIUC, update job is currently running
https://ci.jenkins-ci.org/job/infra_update_center_v3/
2015-12-17 21:42 GMT+01:00 Slide :
> I've seen it take up to 24 hours...
>
> On Thu, Dec 17, 2015 at 1:06 PM Marc Carter wrote:
>
>> Ok. I'll hold off on the Issues issue and see how it goes.
>>
>> ez-tem
On 17.12.2015, at 21:06, Marc Carter wrote:
> ez-templates-1.1.1 has still not emerged into the update center!
We're having some issues with the update site generation right now. If you're
really bored, monitor https://ci.jenkins-ci.org/job/infra_update_center_v3/
--
You received this messag
On 17.12.2015, at 22:03, Daniel Beck wrote:
>
> On 17.12.2015, at 21:06, Marc Carter wrote:
>
>> ez-templates-1.1.1 has still not emerged into the update center!
>
> We're having some issues with the update site generation right now. If you're
> really bored, monitor https://ci.jenkins-ci.o
Renamed repo to https://github.com/orctom/build-timestamp-plugin.git
On Thursday, December 17, 2015 at 8:58:28 AM UTC+8, Daniel Beck wrote:
>
> We generally fork existing plugin repositories. So just start work in a
> repo under your user account, and once you have an initial version, we can
> f
I wanted to introduce a bit of an experimental plugin for
workflow: https://github.com/jenkinsci/pipeline-editor-plugin
(details in the README.md).
The basic idea is to support a very small subset of workflow, which is
stored in a model, and outputs executable workflow script (you can try it
Complicated question. `node` blocks do create `Task`s which are fed to the
`Queue`. There is not currently any way to decorate the resulting
`Queue.Item`s with `Action`s, which you would need to do what you are
attempting.
But do you really need to throttle individual blocks? If not, look for the
32 matches
Mail list logo