+1 Kevin!
If such a bug can help ALL projects work better, LETS DO IT! :)
Correct, Amelia.
I was only pointing out that we needed to create a bugzilla for a
similar type of problem. The issue we're experiencing with Jenkins
is different from the one we've been driving from MicroProfile. I
was just using it for comparison. --------------------------------------------------- Kevin Sutter STSM, MicroProfile and Jakarta EE architect e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutterFrom:
Amelia
Eiras <aeiras@xxxxxxxxxxxxx>To:
EE4J
PMC <ee4j-pmc@xxxxxxxxxxx>Cc:
Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>,
Eclipse Webmaster <webmaster@xxxxxxxxxxxxxxxxxxxxxx>Date:
08/22/2019
05:03 PMSubject:
[EXTERNAL]
Re: [ee4j-pmc] Read access to Jenkins for all committersSent
by: ee4j-pmc-bounces@xxxxxxxxxxx Kevin and all, The bug fixing issues on how git INFRA_
related to ALL Projects hosted under the Eclipse foundation is moving ahead
nicely. Latest update arrived this week. the
EF webmasters have been wonderful at each turn. I will add them via cc'd
to this thread instead of making Wayne that very not scalable. There is no need to open a new
ticket: https://bugs.eclipse.org/bugs/show_bug.cgi?id=483563Happy Thursday Jakartees, Amelia
Eiras https://twitter.com/ameliaeirasTribe: https://tomitribe.com https://tribestream.ioOSS: https://tomitribe.io https://microprofile.ioOn Aug 22, 2019, at 2:48 PM, Kevin Sutter
<sutter@xxxxxxxxxx>
wrote:Scott, I totally agree. We've run into several situations during the Jakarta
EE 8 effort where not having the ability to even look at other jobs has
slowed us down.
But, my guess is that we need to file a bugzilla report to request this.
We raised a semi-related bugzilla report to allow non-committers
the ability to modify issues for MicroProfile. That issue is still
being worked since nothing is as easy as it sounds...
Unless Wayne chimes in that this can be done immediately, I think the bugzilla
approach is the right way to go...
--------------------------------------------------- Kevin Sutter STSM, MicroProfile and Jakarta EE architect e-mail:
sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutter
From: Scott
Stark <starksm64@xxxxxxxxx> To: EE4J
PMC Discussions <ee4j-pmc@xxxxxxxxxxx> Cc: Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx> Date: 08/22/2019
11:53 AM Subject: [EXTERNAL]
[ee4j-pmc] Read access to Jenkins for all committers Sent by: ee4j-pmc-bounces@xxxxxxxxxxx
The inability for any committer to go into the Jenkins CI environments
and look at a job configuration continues to hamper the ability of anyone
to assist with questions on build problems. The question of having read
access for every committer has been floated, but not explicitly raised,
so I’m raising it now.
What can be done to allow every ee4j project committer to have read access
to every ee4j CI instance so that one can at least view the job configurations
on every project job?
_______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc_______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________ ee4j-pmc mailing list ee4j-pmc@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
|