March 2012 - jbosstools-dev - Jboss List Archives

jbosstools-3.3_trunk.aggregate - Build # 4277 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4277 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4277/ to view the results.

12 years, 8 months

1
0
0 / 0

Re: [jbosstools-dev] Who uses .target file?

by Max Rydahl Andersen

please stop just replying to me ;) cc'ing jbosstools dev > On 03/15/2012 12:11 PM, Max Rydahl Andersen wrote: >> That is fine for generating the updatesite - but this does not control the resolution of features/plugins when actually building with tycho. > Yes it does. Tycho resolves against given update-site, and local repo. > On a clean repo, tycho won't visit other sources than the one you give him (the update-site), so we are sure it will use features/plugins from this site. If we control the site, we control what Tycho can resolve. Not true. Read tycho-dev about plan mode. And sure - if I remove all my mirrors from settings.xml, do not build other plugins than from one specific branch/trunk on my machine with the same ~/.m2/repo in it then you are correct. But that is *not* what happens. We build from multiple branches, we want to use mirrors (and those mirrors can get out of date and thus build should fail if thats the case) and I don't have enough disk space to have a ~/.m2/repo for each build. /max

12 years, 8 months

2
2
0 / 0

Re: [jbosstools-dev] Who uses .target file?

by Max Rydahl Andersen

another missed jbosstools-dev > On 03/15/2012 11:52 AM, Max Rydahl Andersen wrote: >> The beauty is if we have such .target file we can use both in eclipse and tycho and be much more confident we are actually testing/building against the same bits. > The beauty is that if we manage a repo, there is less PITA in maintaining build, and it is easy to create target platform that only relies *only* this repo. Then we are sure that those target platform contains the bits we decided to put in the repo. > We manage bits in a repository, and we can provide subsets of this repo as target platforms. Yes and you are talking about *different* things than what Denis, Rob and I are referring to. You want to make it simpler to create the updatesites used for mirroring - great; you can do what you want there (more or less ;) What we are talking about is *guaranteeing* that Tycho/p2 resolves the same version on each developers/jenkins machine. just using an updatesites does not do that. Plus we are talking about having an easy way to feed the target platform into eclipse so it can be used for testing/development - feature/updatesites does not do that either. /max

12 years, 8 months

1
0
0 / 0

Re: [jbosstools-dev] Who uses .target file?

by Max Rydahl Andersen

you forgot to cc jbosstools-dev. fixed ;) > On 03/15/2012 11:36 AM, Max Rydahl Andersen wrote: >> Don't understand this - having it on an updatesite does not restrict the versions. Feature's neither since they resolve with version ranges. target files can be used to *fixate* the version, making it deterministic. > > The idea here is to fixate the version of plugins and features we want to fixate in the site. It is possible to write a site.xml with a given version of a feature (not 0.0.0 or x.y.z.qualifier, but 3.1.0.v20120316) and also to write feature.xml with explicit versions of plugins. > Then Tycho does not resolve a feature range or a wildcard version, it simply takes the one that is defined in the site.xml or feature.xml. That is fine for generating the updatesite - but this does not control the resolution of features/plugins when actually building with tycho. /max

12 years, 8 months

1
0
0 / 0

updating marketplace and finding things missing

by Max Rydahl Andersen

Hi, Apparently marketplace hadn't taken full effect when I tested since this morning its failing because it is missing a few features that was present in M5: org.jboss.tools.community.central.feature and org.jboss.tools.runtime.feature where did these go and what replaces them ? /max

12 years, 8 months

2
2
0 / 0

jbosstools-3.3_trunk.aggregate - Build # 4273 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4273 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4273/ to view the results.

12 years, 8 months

1
0
0 / 0

jbosstools-3.3_trunk.aggregate - Build # 4266 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4266 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4266/ to view the results.

12 years, 8 months

1
3
0 / 0

New views on public Jenkins

by Nick Boldt

New public views [0] are live on the external-facing Jenkins server: [0] https://ci.jboss.org/hudson/view/JBossTools/ These are to match the equivalent views on the internal Jenkins, for those w/o VPN access such as our community members, contributors, and people who've lost their RSA keys. Hope this will make it easier to see what's going on in the release train / job stack. Note in particular there are widgets for Unstable jobs, Latest builds, and in the Jenkins Job List, we now have Upstream and Downstream columns so you can see if your jobs are properly interconnected. (Should you see anything that looks wrong, don't hesitate to open a JIRA [1].) [1] https://issues.jboss.org/secure/CreateIssue.jspa?pid=10020&issuetype=1 As a reminder, the internal views [2] are here: [2] https://hudson.qa.jboss.com/hudson/view/DevStudio/ -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

12 years, 8 months

1
0
0 / 0

jbosstools-3.3_trunk.aggregate - Build # 4263 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4263 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4263/ to view the results.

12 years, 8 months

1
0
0 / 0

jbosstools-3.3_trunk.aggregate - Build # 4261 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4261 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4261/ to view the results.

12 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev March 2012