.p4ignore #13

  • //
  • guest/
  • perforce_software/
  • helix-web-services/
  • main/
  • .p4ignore
  • View
  • Commits
  • Open Download .zip Download (1 KB)
# Ignore RubyMine files
.idea

# Any directory named 'work' is typically used for downloaded p4d, and 
# p4droots setup by ruby utilities
work

# We'll use this as our default 'local bundler cache' which we use to actually
# create packages that include all their very own gem dependencies.
vendor/cache

# The output of most build commands goes in pkg
pkg

# Temporary files created by the docbook generation stuff
*.pyc

# We use this output directory for specs so that Jenkins can collate the output
spec-output

# Temporary output of the yardoc (Ruby documentation) tasks
.yardoc
doc-output

# Oh, thank you Apple
.DS_Store

.vagrant

# Ignore any package files that might have been put into the source directory
perforce*.deb
perforce*.changes

# Working directories used by TestKitchen to generate Omnibus installers in VMs
.kitchen

# Need to make sure helper tools (like RubyMine) do not attempt to check this
# in.
.p4config

# This is set once during the build process, and copied around, but not ever
# checked in.
perforce.rb

# This is a file of versions of the different projects within web services along
# with the configuration file, usable by the bash script. The version numbers
# come from either the Ruby configuration, except for the changelist number,
# which either comes from a p4 command or the environment.
p4ws-versions.sh
# Change User Description Committed
#13 15618 tjuricek By default, writing spec results to spec-output, docs to doc-output.

The archiving in a 'build' branch will be handled by the CD pipeline.
#12 14191 tjuricek Saving Gemfile.lock at top level
#11 13549 tjuricek Remove p4ws-versions.sh which had been incorrectly checked in.
#10 13544 tjuricek Revise package and gem versioning.

Packages will use [gem]-[changelist] as their versions. Gems will use a standard Ruby MAJOR.MINOR.REVISION format.

P4WEBAPI-64
#9 13534 tjuricek Remove automatically generated license files and unused run.sh files.
#8 13520 tjuricek Created a 'cluster' build procedure that creates an installer on build, and executes the install on a test instance.

The main change is to package all gem dependencies via 'vendor/cache' (using the 'bundle package' command).

Right now, there appears to be an issue with test data initialization, which may need a revised approach.
#7 13517 tjuricek Revised Salt hierarchy to allow for CD clustering.

Now, there are two main salt environments: 'build' and 'eval'.

The 'eval' environment can be configured for testing or development by setting the Grain 'dev_pillar: True' or 'test_pillar: True'.

The test modes may need a bit more effort to figure out exactly where I'll put the .deb files. The dev box passes p4_web_api tests.
#6 13512 tjuricek Add 'test-ubuntu12' environment that sets up projects based on "production" packages.

Packages are installed from source files that should have been created by the last 'build-ubuntu12' environment. Since the package building process "dirties" up the environment it's better to use a clean system to test package installation.
#5 13499 tjuricek Simple p4_web_api omnibus installer.

Successfully built using a test-kitchen VM for debian ubuntu 14.04.
#4 13491 tjuricek Minimal .deb installer package for the p4_web_api

The goal of this package is to provide a way of distributing the web application source via deb instead of something like the workshop or git. There will definitely be some changes as a complete deployment workflow is defined.

This includes some vagrant machines for building the installer packages ('ubuntu') and testing out the environment ('salt').
#3 13435 tjuricek Added framework for QtTest to the p4_phoenix_services qt client (and fixing stupid compile errors).

Also, ignoring .DS_Store.
#2 13414 tjuricek Add spec-output to commonly ignored paths
#1 13412 tjuricek Initial version of the web-services mainline.

This is a collection of several projects, that will likely often get released together, though many of them may not always be relevant.

See the README for more information.