On 13.11.2013 03:28, Isaac Isao Saito wrote: > # Just found that Gmail made me reply to Dirk only...Resending. > > Thanks Dirk again. Crystal now. > > One last trivial question; if I choose `Devel` from pre-release web > site interface, does the test work the same as `Latest`, ie. package > build test + downstream build test (and probably many more tests) > using package fetched from devel/source repository? Yes, exactly the same process. - Dirk > > Thank you in advance, > > IsaacS > > On Thu, Oct 31, 2013 at 3:18 AM, Dirk Thomas wrote: >> I have removed all buildfarm related information from the wiki page >> http://wiki.ros.org/bloom/Tutorials/PrereleaseTest since: >> >> * it was pretty wrong and >> * more comprehensive and correct information is already available here: >> http://wiki.ros.org/regression_tests >> >> - Dirk >> >> >> >> >> On 30.10.2013 10:23, Isaac Isao Saito wrote: >>> >>> Thanks Dirk. >>> >>> I still need to ask then; wiki sounds that pre-release test is capable >>> of test with release repository by leaving out the version. Is it not >>> true then? >>> >>> http://wiki.ros.org/bloom/Tutorials/PrereleaseTest#Test_a_package_that.27s_never_been_released_yet >>> # yes I contributed to part of the wiki page with limited understanding... >>> >>> If the answer to my question above is yes, then is the only available >>> pre-release test on buildfarm for packages that haven't been released >>> is development test? I'd just like to clarify that. >>> >>> Thanks again in advance, >>> >>> Isaac >>> >>> #1 By the way is svn not acceptable for devel test? I've asked it awhile >>> ago. >>> >>> http://answers.ros.org/question/88391/format-of-sourceyaml-for-development-test-for-svn/ >>> >>> -- >>> Isao Isaac Saito >>> Phone: +81-80-9657-1303 (Japan) >>> +1-469-688-9008 (US) >>> >>> >>> On Thu, Oct 31, 2013 at 1:32 AM, Dirk Thomas >>> wrote: >>>> >>>> Since you have never released the package "rtmros_nextage" into Groovy >>>> you >>>> can not run a prerelease from the GBP repository. >>>> The fact that the prerelease website offers you "latest" is actually a >>>> bug >>>> and I will make it not offer that (since there is no released version >>>> yet). >>>> >>>> If you want to perform a prerelease from the source repo (before doing >>>> any >>>> release) you have to add you repo to the source.yaml file. >>>> Then you can select the "devel" option on the prerelease website. >>>> >>>> - Dirk >>>> >>>> >>>> >>>> >>>> On 30.10.2013 02:25, Isaac Isao Saito wrote: >>>>> >>>>> >>>>> ROS-Releasers, >>>>> >>>>> I'm gettting an error on the browser when I try to trigger a >>>>> pre-release job for a package that's yet to be released (listed on >>>>> rosdistro without version). Any idea what's wrong? >>>>> >>>>> >>>>> ``` >>>>> Failed...... >>>>> >>>>> We failed to triger your pre-release jobs... Check out the output >>>>> below. >>>>> >>>>> rtmros_nextage (latest) >>>>> >>>>> Traceback (most recent call last): File >>>>> "/var/www/prerelease_website/venv/bin/generate_jenkins_prerelease", >>>>> line 74, in main() File >>>>> "/var/www/prerelease_website/venv/bin/generate_jenkins_prerelease", >>>>> line 68, in main additional_publishers=additional_publishers) File >>>>> >>>>> >>>>> "/var/www/prerelease_website/venv/lib/python2.6/site-packages/jenkins_tools/run_jenkins.py", >>>>> line 87, in run_jenkins_now _update_jenkins_job(jenkins_instance, jc, >>>>> ubuntu_distro, arch, job_name, email, script, script_args, user_name, >>>>> custom_params=params, parameters=parameters, matrix=matrix) File >>>>> >>>>> >>>>> "/var/www/prerelease_website/venv/lib/python2.6/site-packages/jenkins_tools/run_jenkins.py", >>>>> line 74, in _update_jenkins_job >>>>> jenkins_instance.reconfig_job(job_name, job_xml) File >>>>> >>>>> >>>>> "/var/www/prerelease_website/venv/lib/python2.6/site-packages/jenkins/__init__.py", >>>>> line 423, in reconfig_job >>>>> self.jenkins_open(urllib2.Request(reconfig_url, config_xml, headers)) >>>>> File >>>>> >>>>> "/var/www/prerelease_website/venv/lib/python2.6/site-packages/jenkins/__init__.py", >>>>> line 211, in jenkins_open return urllib2.urlopen(req).read() File >>>>> "/usr/lib64/python2.6/urllib2.py", line 126, in urlopen return >>>>> _opener.open(url, data, timeout) File >>>>> "/usr/lib64/python2.6/urllib2.py", line 391, in open response = >>>>> self._open(req, data) File "/usr/lib64/python2.6/urllib2.py", line >>>>> 409, in _open '_open', req) File "/usr/lib64/python2.6/urllib2.py", >>>>> line 369, in _call_chain result = func(*args) File >>>>> "/usr/lib64/python2.6/urllib2.py", line 1190, in http_open return >>>>> self.do_open(httplib.HTTPConnection, req) File >>>>> "/usr/lib64/python2.6/urllib2.py", line 1165, in do_open raise >>>>> URLError(err) urllib2.URLError: >>>>> ``` >>>>> >>>>> I seem to be able to create jobs for released packages. >>>>> >>>>> Thanks! >>>>> >>>>> >>>>> -- >>>>> Isaac >>>>> _______________________________________________ >>>>> ros-release mailing list >>>>> ros-release@code.ros.org >>>>> http://lists.ros.org/mailman/listinfo/ros-release >>>>> >>>> >>>> _______________________________________________ >>>> ros-release mailing list >>>> ros-release@code.ros.org >>>> http://lists.ros.org/mailman/listinfo/ros-release >>> >>> _______________________________________________ >>> ros-release mailing list >>> ros-release@code.ros.org >>> http://lists.ros.org/mailman/listinfo/ros-release >>> >> >> _______________________________________________ >> ros-release mailing list >> ros-release@code.ros.org >> http://lists.ros.org/mailman/listinfo/ros-release > _______________________________________________ > ros-release mailing list > ros-release@code.ros.org > http://lists.ros.org/mailman/listinfo/ros-release >