Skip to content
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

Various build and deploy fixes from the FS branch #627

Merged
merged 6 commits into from Jan 22, 2013

Conversation

joshmoore
Copy link
Member

== Build ==

These are constitute a number of scripts that I've had
for some time locally, but which make server work faster
and therefore should be available for everyone. A general
workflow might be:

cd components/blitz
# Make some change
../../build.py -top hot-blitz

This will:

* Do a proper build of blitz
* Copy the jars to locations under dist/
* Restart just the Java services

Also available are:

* ./build.py -py <target> which replaces
  ./build.py -f components/tools/OmeroPy/build.xml <target>

== Deploy ==

The blitz-gc target is now available for use with bin/omero admin
in order to enable GC logging:

bin/omero admin deploy blitz-gc

Finally, the ignore=dirty .gitmodule statements should make the
output of git status a bit nicer and prevent odd messages on
git commit -a when using hooks.

Previously it was always necessary to be
in the top-level directory for build.py to
work properly. Now, if os.chdir is always
performed to the top-level, and if a build.xml
file is present in the current working dir
(before os.chdir) then it will be passed to
ant as "-f `pwd`/build.xml""

This allows:

  ../../../build.py test

and similar from OmeroPy etc.
Previous minor fixes to build.py allowed called from
anywhere in the source repository. If a build.xml is
present in the current directory, that is used. If not,
then the top-level directory is used. However, there
was no way to use the top-level when a build.xml was
present. `-top` now allows this.
Now, "-fs", "-java", "-cpp", "-web", and "-py"
all run the builds at the proper layer, i.e.
equivalent to:

  ./build.py -f components/tools/X/build.xml
@bpindelski
Copy link

All changes work as expected. The two things I'd probably flag as missing are:

  • missing descriptions in build.xml (hence the new targets aren't visible in the build.py -p output),
  • documentation updates (instances where build.py -f is used).

@joshmoore
Copy link
Member Author

@bpindelski, fair enough. Opened https://trac.openmicroscopy.org.uk/ome/ticket/10236 since the changes will need to go to both branches, and update the submodule.

joshmoore added a commit that referenced this pull request Jan 22, 2013
Various build and deploy fixes from the FS branch
@joshmoore joshmoore merged commit 926a80d into ome:dev_4_4 Jan 22, 2013
@joshmoore joshmoore deleted the build-improvements-pr577 branch March 20, 2013 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants