I am working with a small development team where we are working together on a Worklight V6 Project, where we are using GitHub as our repository. Is there any docs on what artifacts we should be pushing/pulling for a Worklight project with GitHub? Thanks!
JT
As always, the fist place to look is the infocenter. In addition, there are a couple of .jazzignore files that get populated in the project tree, and you should be able to add everything in those into your .gitignore.
I have a somewhat old blog post about using Subversion with Worklight here Some details will be different with Worklight V6 and git, but it should give you some background
Related
I have an existing project that uses project boards on GitHub. I want to move all issues (open and closed) to projects (beta) on GitHub. Is there a way to do that automatically? Right now, I only know how to add issues manually to projects (beta).
As far as I know, there is currently no official guide on how to migrate to GitHub Projects (beta). You might want to follow this discussion on the topic: https://github.com/github/feedback/discussions/6141
However, I created a tutorial on how to migrate from the legacy project boards to the new projects (beta) myself: https://github.com/galargh/projects-migration#how-to-migrate-from-github-projects-to-github-projects-beta
It describes how to migrate cards (including column names) by either running a GitHub Actions workflow or a bash script.
Unfortunately, it does require some manual steps because projects (beta) API is not complete yet - the project itself and the Status field options have to be created manually to be precise.
After the migration, I'm also heavily using this action I created https://github.com/protocol/github-api-action-library/tree/master/add-project-items-by-content-query. I use it to periodically populate my projects based on content search queries (e.g. I automated adding all the issues that mention me - https://github.com/galargh/.github/blob/684c316/.github/workflows/add-project-items.yml).
I implemented python script that helps you migrate your project (similar to #galargh's solution) which uses the GraphQL api for the old projects too (might be more future proof) and also allows you to map column names and migrate PRs.
https://github.com/doidor/gh-projects-migration
You can now do this by enabling the Project migration feature in feature preview
Once you enable it you should see a Start migration button when you go to your Classic (not beta) Project Board
Here are the official docs on how to do it
i have laravel 5.3 project files in developement phase long way to go on live. now one more developer joined me with this. i want share my project via github version control so that we both work on same project without any conflictions. can anyone help me with this how to do it ?
As of now this is not go to the live server.
I am assuming you know git-branching
Also check this
Git branch strategy for small dev team
I have a couple of Eclipse extension projects hosted on GitHub. The problem is that I can't see where to host the related update site. It is in fact not possible on GitHub to have a direct url (raw) to a folder (the UpdateSite PRoject) as you can see here GitHub: URL to raw files. It seems the same thing holds for Google Drive :(
A couple of options I guess: SourceForge, Amazon S3 (with CloudFront), Bintray.
UPDATE:
I switched to GitHub Pages after Bintray has shut down.
This is the new post about that:
https://www.lorenzobettini.it/2021/03/publishing-an-eclipse-p2-composite-repository-on-github-pages/
OLD:
I now use bintray and I documented the whole process for publishing a composite update site to bintray here: http://www.lorenzobettini.it/2016/02/publish-an-eclipse-p2-composite-repository-on-bintray/
OLD 2:
I use sourceforge for the update site (aka p2 repository) of all my projects. I recently published a blog post detailing all the steps to achieve that http://www.lorenzobettini.it/2015/01/publish-an-eclipse-p2-repository-on-sourceforge-with-rsync/
I have recently integrated my Jira Server (4.3.x) with my Bamboo Server (3.1.x) and Subversion server (Collabnet 1.6.x). When I click on the build tab of a project on Jira, it only lists those builds that are linked with a project issue. But I have many builds that are not linked to any of my issues, therefore, those builds are not listed in the build tab of Jira. How can I tell Jira to list me ALL the builds of my project, not only those linked with project issues?
There are pages on Atlassian's JIRA and Bamboo documentation wikis about doing this see: Browsing a Project's Bamboo Builds (JIRA 4.3 specific) and Integrating Bamboo with JIRA (Bamboo 3.1 specific).
It seems that it is not possible to list all builds of a Jira project performed by Bamboo, on the build tab of a project in jira.
Our development team uses Eclipse + Aptana to do their web development work. Currently, most of them are mapping their Eclipse projects directly to the web server. I'd rather them create a local project and use that to sync to the web server project directory they are working on.
The issue is that there aren't any good solutions which is just appalling given the popularity of the two.
The FileSync plugin for Eclipse is only one-way. Meaning if another developer makes a change to the file on the server, another dev isn't even notified and could overwrite the change.
The File Transfer option in Aptana 2.0 doesn't support any sort of Sync, just manually uploading/downloading files.
The Sync option in Aptana 1.5.1 doesn't allow you to merge files when they are different. You can only update one or the other. It does however allow you to view a diff (but only if you right click and select) and in that diff you can't make any changes.
I did find a way to allow files to be uploaded to their Sync repositories in Aptana using Eclipse Monkey. However it doesn't work if a user saves multiple files at once, 'Save All', again it doesn't work. And additionally, there is no notification if a user opens a local file that has an updated copy on the server. I tried to add one using Eclipse Monkey but I couldn't find any sort of listener in the Eclipse API to do it and any Eclipse Monkey documentation is far and few between.
My only solution at this point is just to let them continue to map directly to the server or ask them to do a manual download before they do any work (but again what if someone uploads a change right after they do that).
Anyone have any ideas?
April 2010
Add EGit to your Eclipse+Aptana setup, and:
let developers push to a local bare repo their developments (see also this post)
let your local project be updated by a git pull from that same local bare repo (creating/updating) a local working directory with sources merged/updated (or by using a post-update hook as described in my previous SO link)
let your local Aptana+Eclipse(+EGit) reference that local working directory, also used by your web server.
In short, when you are speaking of file synchronization + merges, this is a job for a (D)VCS (Version Control System: Centralized or Distributed VCS)
Oct 2011: as xmedeko mentions in the comments, Aptana3 has its own Git plugin.
And it isn't very compatible with EGit: See bug 1988.
Adding to VonC answer (which is correct IMHO), what probably lies beneath this scenario is that the process you adopted is not correct in itself, apart from the tools used.
If I understood well, you should not allow nor perform a direct upload from a development version of the project to the web server. Merging is not a job for remote synchronization tools, and it should happen well before the deployment phase (upload to web server is practically a deploy).
You should have a dedicated repository taken from some point in development history (according to you release timeline), a point where merge has already happened. Then deploy it (by means of file synchronization if you want, but that is not mandatory) on a local/staging web server.
Perform there any test you run on the web site actively running (i.e. integration and/or functional tests). If there's any bug & fixing, well there are different ways to actually apply the fixes on development & staging code repository. Only after that, you deploy the staging repository on to production web server (again, synchronization tools are a way to do that).