New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated commands look the same no matter what branch option selected #31
Comments
I can confirm that the version selection doesn't work at the moment. It seems to be a regression of the "new" UI. @wjwwood Can you please look into this at some point. |
I'll try to have a look at it soon. |
It doesn't look like the underlying Currently, I believe it will always checkout code as defined in the @dirk-thomas Can you speak to whether or not the But I couldn't find anything that lead me to a way to accomplish this. I think something could be done with the |
That explains to me why prerelease stops with error saying like the following for a repo without source entry, even though on prerelease web i/f I selected
|
The script
Using those the generated command lines for the some other examples (since
As you can see in the last two commands each package is being identified individually. |
The use of
This would work, but I think the important thing to point out is that rather than specifying the repository name (as is the case for I think |
I just made up |
(May or may not be related to #14)
I flipped
devel
andlatest
but in the end I seem to have gotten the exactly same command.generate_prerelease_script.py https://raw.githubusercontent.com/ros-infrastructure/ros_buildfarm_config/production/index.yaml jade default ubuntu trusty amd64 moveit_core --level 0 --output-dir .
generate_prerelease_script.py https://raw.githubusercontent.com/ros-infrastructure/ros_buildfarm_config/production/index.yaml jade default ubuntu trusty amd64 moveit_core --level 0 --output-dir .
Also chose specific version tag but it looks the same again.
generate_prerelease_script.py https://raw.githubusercontent.com/ros-infrastructure/ros_buildfarm_config/production/index.yaml jade default ubuntu trusty amd64 moveit_core --level 0 --output-dir .
Question: Will the result of these command be actually different with these commands (if so, the change is embedded somehow somewhere invisible from the command)?
The text was updated successfully, but these errors were encountered: