Re: jbosstools-discovery/pull/299 nothing pings those URLs. They're
only there so when a user clicks on a certification link for more
info, they get a page opened in a browser. None of the install tests
will catch what happens when a user clicks on a "more info" link. :D
Re: jiras for install grinder, yes. There are a few. There are also
eng-ops tickets.
On Mon, Sep 7, 2015 at 3:52 AM, Max Rydahl Andersen <manderse(a)redhat.com> wrote:
Hey,
We have our install-grinder and p2 install tests to catch errors but
I don't notice them being mentioned when what looks like actual basic
p2/metadata
errors are fixed.
i.e.
https://github.com/jbosstools/jbosstools-discovery/pull/299 simple
issue, simple fix.
But was this caught by p2 install and install-grinder ?
- if not, why not ? This seems like one that should have been easily
caught.
- if yes, why first now ? We made this change to sites a while ago
(JBDS-3208 was resolved end-of-june)
Looking at the logs of install-grinder
(
https://ci.jboss.org/hudson/job/jbosstools-install-grinder_master/ or
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g...)
it shows perfect blue since Jun 13 2014.
So my assumption is that it was *not* caught.
Nick/Mickael - how come install-grinder can pass when the repos it is
supposed to point to are 404 ?
If it's because the tests are using intermediary build urls then it
sounds like we are missing an actual test for the
released bits as opposed only having for our current build ?
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com