• 强烈要求北京也设点。。。。

  • 外包 at 2015年02月02日

    楼上就是爱奇艺吧?

  • 六百字读懂 Git at 2015年01月28日

    很好的文章,好好理解理解诶

  • 六百字读懂 Git at 2015年01月28日

    英文版

    Git in six hundred words (This essay is a companion piece to Gitlet, my implementation of Git in JavaScript.)

    Imagine you have a directory called alpha. It contains a file called number.txt that contains the text first.

    You run git init to set up alpha as a Git repository.

    You run git add number.txt to add number.txt to the index. The index is a list of all the files that Git is keeping track of. It maps filenames to the content of the files. It now has the mapping number.txt -> first. Running the add command has also added a blob object containing first to the Git object database.

    You run git commit -m first. This does three things. First, it creates a tree object in the objects database. This object represents the list of items in the top level of the alpha directory. This object has a pointer to the first blob object that was created when you ran git add. Second, it creates a commit object that represents the version of the repository that you have just committed. This includes a pointer to the tree object. Third, it points the master branch at the new commit object.

    You run git clone . ../beta. This creates a new directory called beta. It initializes it as a Git repository. It copies the objects in the alpha objects database to the beta objects database. It points the master branch on beta at the commit object that the master branch points at on the alpha repository. It sets the index on beta to mirror the content of the first commit. It updates your files – number.txt – to mirror the index.

    You move to the beta repository. You change the content of number.txt to second. You run git add number.txt and git commit -m second. The commit object that is created has a pointer to its parent, the first commit. The commit command points the master branch at the second commit.

    You move back to the alpha repository. You run git remote add beta ../beta. This sets the beta repository as a remote repository.

    You run git pull beta master.

    Under the covers, this runs git fetch beta master. This finds the objects for the second commit and copies them from the beta repository to the alpha repository. It points alpha’s record of beta’s master at the second commit object. It updates FETCH_HEAD to show that the master branch was fetched from the beta repository.

    Under the covers, the pull command runs git merge FETCH_HEAD. This reads FETCH_HEAD, which shows that the master branch on the beta repository was the most recently fetched branch. It gets the commit object that alpha’s record of beta’s master is pointing at. This is the second commit. The master branch on alpha is pointing at the first commit, which is the ancestor of the second commit. This means that, to complete the merge, the merge command can just point the master branch at the second commit. The merge command updates the index to mirror the contents of the second commit. It updates the working copy to mirror the index.

    You run git branch red. This creates a branch called red that points at the second commit object.

    You run git checkout red. Before the checkout, HEAD pointed at the master branch. It now points at the red branch. This makes the red branch the current branch.

    You set the content of number.txt to third, run git add numbers.txt and run git commit -m third.

    You run git push beta red. This finds the objects for the third commit and copies them from the alpha repository to the beta repository. It points the red branch on the beta repository at the third commit object, and that’s it.

  • 那你权限到底给了没有?

  • 你这里的 release 也只是一种临时性的 dev 分支,并不是 release

    你这里的 master 并不是发布的主分支,只是个大杂烩。 这里的 dev 更像是发布分支,因为只要 dev 足够的稳定,就可以直接发布。

    你这里的问题是 1)dev 虽然从 master 拉出来却不直接合并回去 2)dev 和 release 并没有直接的关系,却分支之间进行了合并

  • 不试试无法排除问题。

    另外就是可以映射到一个盘符,然后在进去执行这个命令,如下

    net use H: %Server%\Deployment_Staging %GlobalPassword% /USER:%GlobalUserName% H: rd /s /q "%Server%\Deployment_Staging\Deploy"

  • 把这些保存成一个 bat 文件,双击运行是成功的还是失败的?

  • 编译完成后拷贝到服务器上,然们去取就可以了。没必要提交到 SVN 里

  • 编译完的东西为啥要提交到 svn 里?

    这台机器不信任 svn 服务器,因为 svn 服务器开启了 SSL。需要让这台机器信任 svn 服务器的 SSL 证书。具体你可以搜搜。

  • 还有一个问题,怎么会在 hudson 中用 svn import?

  • 我个人认为一般需要自动 merge 的动作,证明分支策略是需要再研究研究的。

    你这个要求是要求自动从 02 到 01 的合并?

  • 错误信息是?贴个 log 上来

  • Ant check file length / empty at 2015年01月09日

    zixing :


    <!-- 清理 class 文件 -->

    帮我看个问题吧,谢谢

    我是希望 ${arg2}的内容长度大于 20 再执行 clean 可是经过测试条件没起作用 帮我看一下,是哪的问题呢?

  • Ant check file length / empty at 2015年01月08日

    或者用 size

  • [i=s] 本帖最后由 laofo 于 2015-1-5 16:36 编辑

    呵呵,最近又新成立了个公司么?

  • 恩,限制 list 权限

  • 年底了,大家都开始蠢蠢欲动了。。。

  • windows 上没读权限是写不了的吧?

  • 真的。。。。。你贡献了多少?我是一点都没贡献。

  • 你是说国美的销量?还是国美的工资?

  • 果真是上海:http://new.abb.com/se/jobba-hos-oss/jobbannonser/details/56190775/senior-configuration-management-engineer

    Plats:Shanghai,Shanghai,China Anställningsform:Regular/Permanent Publiceringsdatum:2014-12-16 Kompetensområde:Research and Development Annons-ID:CN56118233_E1

  • 上海?最重要的工作地点没说

  • Docker 101:介绍与入门体验 at 2014年12月11日

    Docker 101: What it is and why it’s important

    Docker is a hot topic this week. If you’re unfamiliar with what this technology is or what it means for your business, here’s a guide.

    What is it?

    Docker is both an open source project and the name of a startup that focuses on Linux Containers. Containers are the idea of running multiple applications on a single host. It’s similar to compute virtualization, but instead of virtualizing a server to create multiple operating systems, containers offer a more lightweight alternative by essentially virtualizing the operating system, allowing multiple workloads to run on a single host.

    Why all the hype?

    Docker the company has released the 1.0 version of its product this week (read more about the 1.0 release here), and in conjunction with doing so is hosting an event named DockerCon. Docker Founder and CTO Solomon Hykes said the open source Docker project has been downloaded (for free) more than 2.75 million times and more than 460 contributors helped create this version. Docker has built up partners to support its product and service providers are jumping on board to offer Docker services. [attach] 2517[/attach]

    Where did containers come from?

    Containers, and specifically Linux containers, are not new. Tech giants such as Oracle, HP and IBM have been using containers for decades. In recent years, though, the open source project Docker has gained popularity as an alternative, or complement to virtualization. Recognizing a market opportunity to provide support around the open source project, a company named dotcloud was formed, but was renamed Docker. In January the company received a Series B funding round worth $15 million, led by Greylock Partners. Red Hat has committed a major investment in the company as well. (Read more about Red Hat’s work with Docker here.)

    • MORE FROM NETWORK WORLD: 12 cloud computing companies worth watching +

    How do they work?

    The open source project has two major aspects: cgroups, or Control Groups, which define the compute, memory and disk i/o that a workload needs; and namesakes, which isolate and separate each of the workloads.

    Docker the commercial product has two major components as well: Docker Engine, which is the core software platform that enables users to create and use containers; and Docker Hub, a SaaS-based service for creating and sharing Docker services. With the release of the 1.0 version and Docker Hub, the company says it has more than 14,000 applications that can be used with its containers.

    Are containers a VM killer?

    Writes tech blogger Scott Lowe. “Containers, on the other hand, generally offer less isolation but lower overhead through sharing certain portions of the host kernel and operating system instance.” Containers are an attractive option for environments where there is only a single operating system, whereas virtual machines and hypervisors can be useful if there is a need to run multiple OSs in an environment. VMs are not going away, but containers could offer a better way to run certain applications instead of virtualization. (Read more about how containers can replace VMs here.)

    What are they used for?

    One of the major benefits of containers is portability. Containers can run on top of virtual machines, or bare metal servers. They can run on-premises or in the cloud. This has made one of the earliest popular use cases of containers be around software development. Coders can write applications, place it in a container, and then the application can be moved across various environments, as it is encapsulated inside the container.

    How much does it cost?

    Docker the open source project is free to download from GitHub. Docker the product offers privately hosted repositories of containers, which are about $1 per container. See full Docker pricing here.

    Who else is involved?

    With all the buzz around Docker, many tech companies are looking to get in on the action. Docker is building up its partnerships, too. The commercial version of Docker comes with support from the company, and integrations with a variety of other software platforms, including Linux distros from Red Hat, SuSE and Ubuntu, and other services like scheduling tools such as Puppet, Chef, Ansible and Jenkins.

    Other service provider vendors are enabling Docker on their platforms. Rackspace CTO John Engates, for example, wrote a blog post this week saying that initially he and the cloud hosting company were not terribly impressed with Docker. But then after customers started using it and asking for Rackspace to support it, the company was “pulled” into the community, Engates says. Now, they’re converts; Engates calls containerization “next generation virtualization.”

    Rackspace is using Docker to test and deploy new applications in various environments; it’s even using containers in networking, because it allows for multi-tenancy of software-based load balancers. The biggest impact though, he says, could be the way containers could usher in an era of portability of workloads across environments. “Docker could provide the abstraction that makes swapping workloads between clouds possible. They don’t have to be OpenStack clouds either. OS-level virtualization makes the application agnostic to the underlying infrastructure. Docker could enable spot markets for cloud computing and the ability for users to find a best-fit solution for their needs.”

    He goes on to list some of the ways users can get involved in the Docker community if they’re interested.

    Brandon Butler Brandon Butler — Senior Writer

    Senior Writer Brandon Butler covers the cloud computing industry for Network World by focusing on the advancements of major players in the industry, tracking end user deployments and keeping tabs on the hottest new startups. He contributes to NetworkWorld.com and is the author of the Cloud Chronicles blog. Email him at [email] bbutler@nww.com[/email] and follow him on Twitter @BButlerNWW.

    转自:http://www.networkworld.com/article/2361465/cloud-computing/docker-101-what-it-is-and-why-it-s-important.html

  • 案例可以参考 android 和 github