Playing around with Deisgner 4.8 from the Early Access refresh and having watched the demo video, I'm still wondering what development workflow is envisioned by using git for packages. The demo shows how to build and publish packages to git but not how to pull packages out of it again.
Looks like Designer does not store packages in git in as a Package Update Repo (i.e. with site.xml and features/plugins/deprecations subfolders) but only as plugin jars in a flat folder (like in the "plugins" subfolder of an Online Repo) so a git working tree cannot be used as a local Online Repository in Designer.
Git is about sharing with others, so how am I supposed to use a package someone shared through a git repo with me in my Designer projects? Manually import the file into each project's Package Catalog?
I also do not get the idea of both building and publishing to a git repo? Up until now I thought of a git package repo as an alternative to Online Repositories and do not (yet) see a point in putting unreleased packages (that might have their content and build number changed anytime and therefore may cause trouble if distributed and deployed/imported to/from any project other than the one where the package is developed).
Personally I never distribute unreleased packages because their content may change and older build are usually not available anymore. How do others work with unreleased packages? Do you see a use case to put them under version control and share them? How does your dev workflow looks like in that case?
I have not had a look at the 4.8 yet but in one project I work with packages and svn.
Here we never release anything and just use svn for the packages. This to me is not ideal.
I would prefer if designer could split out the packages so they were not checked in at all.
I n my imagination it would be easier to have a packet management tool and use build/release/publish for packages and the normal git for the driverset.
I suppose you can use un-released packages between dev and test, and then only release the package for acceptance.
But yes, I had the same kind of questions when I read about it.
Does it make sense for your awesome Parcel Service tool to be enabled to copy between File based Repo's and GIT based repos? That would be pretty cool.
I do not understand how GIT is supposed to be used in the 4.8 Designer.
Can anyone give me an URL to the demo video referenced in the orignal post?
I have not yet tried it. But the idea is, ONLY Package repos can be in GIT. Rest of the project, nope, SVN is only option, and it is less than optimal.
As Lothar said in a previous post, it basically treats GIT as a file system to write a Repo to, and check out from.
Then to push the repo to a server to 'publish' for others to use?
I finally found the option to build packages to cloned GIT-reop when building packges.
I.e. it's really a very limited support, building to a folder, and staging the file.
I don't see any reasonable use for this functionlity.
Why should I backup my jar-files in GIT?
I build them to a folder on a server, which is backed up.
If I want to publish them, I guess I can publish the folder either on a file-server or a web-server.