I have already installed clio(acumos 3rd version) successfully but I faced some issues in creating pipeline, so I want to upgrade to "demeter" release.
In order to install "demeter" release of acumos, I did
git clone --single-branch --branch demeter https://gerrit.acumos.org/r/system-integration
~/system-integration$ git branch
demeter
~/system-integration$ git status
On branch demeter
Your branch is up to date with 'origin/demeter'.
But the content of environment files suggests it still a clio version code
~/system-integration/AIO/acumos_env.sh
Version of the AIO toolset
export ACUMOS_AIO_VERSION=3.0.3
export PORTAL_BE_IMAGE=$ACUMOS_STAGING/acumos-portal-be:3.0.24
export PORTAL_FE_IMAGE=$ACUMOS_STAGING/acumos-portal-fe:3.0.24
How can I make sure, It installs all demeter related images ?
ex:
nexus3.acumos.org:10002/acumos/acumos-portal-be:4.0.14 4.0.14
in Demeter AIO is deprecated, the new installer is z2a. there is a folder called z2a in system-integration.
Related
There is a github repository that is no longer actively maintained. I want to use the code and move it into my project's components but that is tedious and not sure if that is the best approach.
I just want to bump the version of draftjs used by the repository.
Here is the repo and it uses draft js version 0.10.0
https://github.com/brijeshb42/medium-draft
My local project uses draft js version 0.11.7
This causes errors and incompatibility issues.
What is the best approach when a repository uses an outdated version of a repository used by local project?
Before forking and publishing to npm your own version of that dependencies, you might consider using the package/patch-package
Patches created by patch-package are automatically and gracefully applied when you use npm(>=5) or yarn.
No more waiting around for pull requests to be merged and published. No more forking repos just to fix that one tiny thing preventing your app from working.
# fix a bug in one of your dependencies
vim node_modules/some-package/brokenFile.js
# run patch-package to create a .patch file
npx patch-package some-package
# commit the patch file to share the fix with your team
git add patches/some-package+3.14.15.patch
git commit -m "fix brokenFile.js in some-package"
In your case, you would be patching the brijeshb42/medium-draft/package.json file.
The Git Source Code Mirror on GitHub (https://github.com/git/git) says that the most recent version of Git is 2.7.4. I'm using EGit 3.5.2 on Spring Tool Suite (Eclipse Luna SR1), so that version number obviously doesn't correspond to a Git version. Is there any way to trace back what version of Git this version of EGit is based off of?
I checked here, but it only maps versions of EGit to versions of Eclipse...
https://wiki.eclipse.org/EGit/FAQ#What_is_Git.3F
As you noticed, EGit does not appear to be based on a particular version of Git. The EGit documentation has the following to say:
How compatible is EGit with Git?
Some, but not all configuration options/features in Git are available in EGit/JGit. Here is a summary, not yet complete describing some of these, including notable differences. Note that the set of EGit/JGit is not based off a particular Git version.
Practically speaking, as long as you are using the most recent version of Git, you should be OK. This is because Git itself should be backwards-compatible with whatever version of Git was concurrent with the particular release of EGit which you are using. But I would not recommend the other way around, e.g. using the first release of Git from many years ago with the latest EGit plugin.
There is no correlation between EGit and Git versions. EGit uses JGit, a pure Java implementation of the Git VCS, to access repositories. JGit versions do not follow a specific Git versions either. Though JGit is relatively on par with Git, some things are missing, for example git clone -- depth. Unfortunately, a detailed comparison does not exist
How to fix this problem?
Warning: EGit couldn't detect the installation path "gitPrefix" of native Git. Hence EGit can't respect system level
Git settings which might be configured in ${gitPrefix}/etc/gitconfig under the native Git installation directory.
As I suggested in "Egit installation path error", it can be linked to the absence of a Git installation (which EGit relies on for the system config path).
Install:
Git as a portable msysgit if you are on Windows: PortableGit-1.8.4-preview20130916.7z (unzip it anywhere you want, and add the C:\path\to\PortableGit-1.8.4-preview20130916\bin to the PATH environment variable)
Or Git using the latest Git Releases from a custom PPA (Personal Package Archive) if you are on Linux
In my case installation of the latest Git version helped.
Downloaded latest version from https://git-scm.com/download/win and installed it to the same directory as Git was before. Started eclipse and error message from Error log disappeared. I have Cygwin64 installed.
I'm new to Jenkins and experimenting at the moment. I use Eclipse and run Git from within Eclipse, using the Git plugin, which is described as follows: 'Eclipse Git is an Eclipse Team provider based on JGit, a pure Java implementation of the Git version control system'.
I've installed the Git plugin for Jenkins but when I go to configure it, Jenkins complains that it can't find the Git executable. That makes sense, and the obvious solution is to install it (in my case, using a Ubuntu repository - sudo apt-get install git-core). My concern is that having two installations of Git on the machine will give rise to problems - or am I being over-cautious?
It's fine to have both - since EGit is pure Java, it has nothing to do with the installed (native code) version of Git.
Problems might arise if there was a breaking change in a future version of Git, but it should be easy enough to fix by updating both installations.
Is there a plugin for Eclipse for git-svn? I'm looking for a way to handle the SVN repo with Git (for fast branch switching etc.)
It does not look like there is a Git plugin for Eclipse that supports git-svn yet.
EGit appears to be the most active and popular Git plugin for Eclipse at the moment and it does not support git-svn, but there isn't anything stopping you from using EGit with Eclipse and interacting with git-svn via command line (or via tortoise git for example).
Eclipse bug 315264 is the EGit bug for supporting git-svn, and it looks like something that the maintainers of EGit are willing implement, but they have other priorities atm. So make sure you vote for this bug if you want the feature.
EGit is the only Git plugin for Eclipse at the moment. It doesn't support git-svn. But there is a way to make EGit work with your Subversion repository and this approach works well with any other Git client.
SubGit is the server-side solution that enables Git access to your Subversion repositories as well as Subversion access to Git repositories. You may refer to SubGit documenation for more details, but in general they are quite straightforward:
$ subgit configure --layout auto $SVN_URL $GIT_REPO
# Adjust $GIT_REPO/subgit/config
# to specify your branches, tags and other settings
# Adjust $GIT_REPO/subgit/authors.txt
# to introduce svn author names to their git counterparts
# Adjust $GIT_REPO/subgit/passwd
# in case you have no SVN credentials cached on your machine
$ subgit install $GIT_REPO
$ ... translating ... a little git is gonna born right here ...
$ TRANSLATION SUCCESSFUL
After that:
You have Git repository at $GIT_REPO synchronized with SVN repository at $SVN_URL; this sync is reliably bi-directional, i.e. both SVN and Git repositories remain writable and SubGit takes care of changes from both sides.
SubGit has installed hooks into $GIT_REPO/hooks directory which are triggered on every git push to that repository.
SubGit polls SVN repository in order to fetch new revisions.
Please note that your teammates may use the same mirror for sending their changes to Subversion repository. In this case you should setup Git server, fortunately, SubGit supports virtually every Git server available at the moment:
Apache HTTP server with git-http-backend, GitLab, Gitosis, Gitolite: supported out of the box;
Atlassian Bitbucket Server: in this case you can use SVN Mirror add-on which is built on SubGit engine;
Gerrit: you'd need to install SubGit plugin for Gerrit in this case;
Disclaimer: I'm SubGit developer; SubGit is commercial software with free options for small teams, Open Source and Academic projects.
Although this question is 4 years old, I thought I would share my recently found workaround:
Open "External Tools Configurations" (right next to "Run
Configurations") and create a new "Program" configuration.
For the working directory, choose your project from the workspace.
Enter svn dcommit into the arguments textfield.
Duplicate the configuration and replace svn dcommit by svn rebase.
Now you can launch git svn dcommit and git svn rebase with two clicks.