GitLab

Fixes a fatal bug for submodule generator support :( .

Utkarsh Ayachit authored Mar 21, 2015 and Kitware Robot committed Mar 21, 2015

2d9efda8

 Fix project name to use "-".
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5

Utkarsh Ayachit authored Mar 21, 2015 and Kitware Robot committed Mar 21, 2015

ab720f86

 doc: Fix path to review merge requests.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4

Utkarsh Ayachit authored Mar 21, 2015 and Kitware Robot committed Mar 21, 2015

a5b757e0 Set correct executable paths for OsX/Windows.
03321b72 Update Qt options to speed up builds (potentially).
ba856959 Fixes Windows issues with moving to non-empty dir.
bec42c89

 Refactored testing.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2

Instead of testing nightly binaries from the website, we now test
binaries generated by the superbuild itself.

Brad King authored Mar 19, 2015 and Kitware Robot committed Mar 19, 2015

1ec99ff1 Documentation: Revise Git development docs to mention fork step
e96ccfd7

 docs: buildbot label is no more
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3

Brad King authored Mar 19, 2015 and Utkarsh Ayachit committed Mar 19, 2015

Also clarify how the main repository and user fork will be referenced
from local clones.
Suggested-by: Dave DeMarle <dave.demarle@kitware.com>

Brad King authored Mar 19, 2015 and Kitware Robot committed Mar 19, 2015

94bf2c39 Consistently refer to the project as ParaView-Superbuild.
01063890 docs: add buildbot information
23d883b8 Documentation: Add links to GitLab markdown documentation
bf08c7fd Documentation: Add ParaViewSuperbuild Git instructions.
aa5c6456 Add README.md and supporting files.
6d5e33fe Add gitattributes.
07c8dda1 Switch developer setup to use the GitLab workflow
8e65e503

 Teach our 'git-gitlab-push' script to push ExternalData content
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1

Port Git instructions from ParaView to ParaViewSuperbuild.

Adding .gitattributes files from ParaView since this project had none.

In SetupForDevelopment, switch from setup-gerrit to setup-gitlab.
Also invoke setup-upstream to switch the "origin" remote to GitLab.
Update the version of the SetupForDevelopment script so that existing
work tree hooks will ask developers to run the script again.

Brad King authored Mar 05, 2015 and Utkarsh Ayachit committed Mar 19, 2015

Teach the git-gitlab-push script to push refs/data/* references
to the remote repository along with the topic.

* setup:
  git-gitlab-push: Require a '--force' option to force-push the topic
  git-gitlab-push: Document options on multiple lines in usage
  git-gitlab-push: Keep user fork 'master' up to date if possible
  git-gitlab-push: Print follow-up instructions and links for user
  Add 'git-gitlab-push' script to help users push to their GitLab fork
  Add 'setup-gitlab' script to configure GitLab access
  Add 'setup-upstream' script to help users configure preferred upstream
  git-gerrit-push: Fetch 'master' before checking refspecs
  git-gerrit-push: Avoid bash history expansion
  git-gerrit-push: Append topic to refspecs instead of overwriting
  git-gerrit-push: Refine topic name validation
  setup-hooks: Create .git hooks directory if necessary

In preparation for making ParaViewSuperbuild development scripts mirror
VTK/ParaView source trees, moving Scripts/GitSetup to
Utilities/GitSetup.

Do not allow users to risk losing work by default.  Our workflow does
not involve pulling first to avoid a non-fast-forward, so hide any such
advice that Git may generate.  Instead add our own advice.

This will allow a longer total set of options without long lines.

If the user pushes to the expected GitLab repository, extract their
username and use it to print URLs useful for them to follow up in
GitLab.

Copy the 'git-gerrit-push' script and change the default remote name.
Also change the topic push refspec to force-push a real branch instead
of the Gerrit "for/" namespace.

Interactively prompt the user with GitLab setup instructions.
Base the script on 'setup-gerrit'.

Interactively prompt the user based on their current configuration
to ask about using the preferred upstream configuration.

Fetch 'master' before deciding if there are no refspecs because later
changes may use 'master' to compute more refspecs.

Protect '!' characters in single quotes.

Other logic may later be added to add more refspecs.

Added a mechanism to use existing ParaView source checkout. This will
make testing with user forks easier.

To specify as PARAVIEW_SOURCE_DIR, one has to ENABLE_paraview and then
turn off ParaView_FROM_GIT and enable ParaView_FROM_SOURCE_DIR.

Change-Id: I73622f63a862d1196bc449e77de78b90b538d82f

Change-Id: If55cd5a117053ca669a4605695bab737a58ac809

Use bash features instead of 'sed'.